Adaptive management of antennas in the network of moving things

ABSTRACT

Methods and systems are provided for adaptive management of antennas in a communication network comprising a complex array of both static and moving communication nodes (e.g., a network of moving things, which may be a vehicle network, a network of or including autonomous vehicles, etc.).

CLAIM OF PRIORITY

This patent application makes reference to, claims priority to andclaims benefit from U.S. Provisional Patent Application Ser. No.62/340,838, filed May 24, 2016. The above identified application ishereby incorporated herein by reference in its entirety:

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This patent application is related to:

-   The present application is related to U.S. Provisional Application    Ser. No. 62/221,997, titled “Integrated Communication Network for a    Network of Moving Things,” filed on Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,016, titled “Systems    and Methods for Synchronizing a Network of Moving Things,” filed on    Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,042, titled “Systems    and Methods for Managing a Network of Moving Things,” filed on Sep.    22, 2015;-   U.S. Provisional Application Ser. No. 62/222,066, titled “Systems    and Methods for Monitoring a Network of Moving Things,” filed on    Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,077, titled “Systems    and Methods for Detecting and Classifying Anomalies in a Network of    Moving Things,” filed on Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,098, titled “Systems    and Methods for Managing Mobility in a Network of Moving Things,”    filed on Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,121, titled “Systems    and Methods for Managing Connectivity a Network of Moving Things,”    filed on Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,135, titled “Systems    and Methods for Collecting Sensor Data in a Network of Moving    Things,” filed on Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,145, titled “Systems    and Methods for Interfacing with a Network of Moving Things,” filed    on Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,150, titled “Systems    and Methods for Interfacing with a User of a Network of Moving    Things,” filed on Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,168, titled “Systems    and Methods for Data Storage and Processing for a Network of Moving    Things,” filed on Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,183, titled “Systems    and Methods for Vehicle Traffic Management in a Network of Moving    Things,” filed on Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,186, titled “Systems    and Methods for Environmental Management in a Network of Moving    Things,” filed on Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/222,190, titled “Systems    and Methods for Port Management in a Network of Moving Things,”    filed on Sep. 22, 2015;-   U.S. Provisional Patent Application Ser. No. 62/222,192, titled    “Communication Network of Moving Things,” filed on Sep. 22, 2015;-   U.S. Provisional Application Ser. No. 62/244,828, titled “Utilizing    Historical Data to Correct GPS Data in a Network of Moving Things,”    filed on Oct. 22, 2015;-   U.S. Provisional Application Ser. No. 62/244,930, titled “Using    Anchors to Correct GPS Data in a Network of Moving Things,” filed on    Oct. 22, 2015;-   U.S. Provisional Application Ser. No. 62/246,368, titled “Systems    and Methods for Inter-Application Communication in a Network of    Moving Things,” filed on Oct. 26, 2015;-   U.S. Provisional Application Ser. No. 62/246,372, titled “Systems    and Methods for Probing and Validating Communication in a Network of    Moving Things,” filed on Oct. 26, 2015;-   U.S. Provisional Application Ser. No. 62/250,544, titled “Adaptive    Rate Control for Vehicular Networks,” filed on Nov. 4, 2015;-   U.S. Provisional Application Ser. No. 62/273,878, titled “Systems    and Methods for Reconfiguring and Adapting Hardware in a Network of    Moving Things,” filed on Dec. 31, 2015;-   U.S. Provisional Application Ser. No. 62/253,249, titled “Systems    and Methods for Optimizing Data Gathering in a Network of Moving    Things,” filed on Nov. 10, 2015;-   U.S. Provisional Application Ser. No. 62/257,421, titled “Systems    and Methods for Delay Tolerant Networking in a Network of Moving    Things,” filed on Nov. 19, 2015;-   U.S. Provisional Application Ser. No. 62/265,267, titled “Systems    and Methods for Improving Coverage and Throughput of Mobile Access    Points in a Network of Moving Things,” filed on Dec. 9, 2015;-   U.S. Provisional Application Ser. No. 62/270,858, titled “Channel    Coordination in a Network of Moving Things,” filed on Dec. 22, 2015;-   U.S. Provisional Application Ser. No. 62/257,854, titled “Systems    and Methods for Network Coded Mesh Networking in a Network of Moving    Things,” filed on Nov. 20, 2015;-   U.S. Provisional Application Ser. No. 62/260,749, titled “Systems    and Methods for Improving Fixed Access Point Coverage in a Network    of Moving Things,” filed on Nov. 30, 2015;-   U.S. Provisional Application Ser. No. 62/273,715, titled “Systems    and Methods for Managing Mobility Controllers and Their Network    Interactions in a Network of Moving Things,” filed on Dec. 31, 2015;-   U.S. Provisional Application Ser. No. 62/281,432, titled “Systems    and Methods for Managing and Triggering Handovers of Mobile Access    Points in a Network of Moving Things,” filed on Jan. 21, 2016;-   U.S. Provisional Application Ser. No. 62/268,188, titled “Captive    Portal-related Control and Management in a Network of Moving    Things,” filed on Dec. 16, 2015;-   U.S. Provisional Application Ser. No. 62/270,678, titled “Systems    and Methods to Extrapolate High-Value Data from a Network of Moving    Things,” filed on Dec. 22, 2015;-   U.S. Provisional Application Ser. No. 62/272,750, titled “Systems    and Methods for Remote Software Update and Distribution in a Network    of Moving Things,” filed on Dec. 30, 2015;-   U.S. Provisional Application Ser. No. 62/278,662, titled “Systems    and Methods for Remote Configuration Update and Distribution in a    Network of Moving Things,” filed on Jan. 14, 2016;-   U.S. Provisional Application Ser. No. 62/286,243, titled “Systems    and Methods for Adapting a Network of Moving Things Based on User    Feedback,” filed on Jan. 22, 2016;-   U.S. Provisional Application Ser. No. 62/278,764, titled “Systems    and Methods to Guarantee Data Integrity When Building Data Analytics    in a Network of Moving Things,” Jan. 14, 2016;-   U.S. Provisional Application Ser. No. 62/286,515, titled “Systems    and Methods for Self-Initialization and Automated Bootstrapping of    Mobile Access Points in a Network of Moving Things,” filed on Jan.    25, 2016;-   U.S. Provisional Application Ser. No. 62/295,602, titled “Systems    and Methods for Power Management in a Network of Moving Things,”    filed on Feb. 16, 2016; and-   U.S. Provisional Application Ser. No. 62/299,269, titled “Systems    and Methods for Automating and Easing the Installation and Setup of    the Infrastructure Supporting a Network of Moving Things,” filed on    Feb. 24, 2016.

Each of the above identified applications is hereby incorporated hereinby reference in its entirety for all purposes.

BACKGROUND

Current communication networks are unable to adequately supportcommunication environments involving mobile and static nodes. As anon-limiting example, current communication networks are unable toadequately support a network comprising a complex array of both movingand static nodes (e.g., the Internet of moving things).

Limitations and disadvantages of conventional methods and systems willbecome apparent to one of skill in the art, through comparison of suchapproaches with some aspects of the present methods and systems setforth in the remainder of this disclosure with reference to thedrawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 2 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 3 shows a diagram of a metropolitan area network, in accordancewith various aspects of this disclosure.

FIG. 4 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIGS. 5A-5C show a plurality of network configurations illustrating theflexibility and/or and resiliency of a communication network, inaccordance with various aspects of this disclosure.

FIG. 6 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 7 shows a flow chart of an example process for automatic andself-healing management of antennas in the network of moving things, inaccordance with various aspects of the present disclosure.

SUMMARY

Various aspects of this disclosure provide communication networkarchitectures, systems and methods for supporting and/or effectivelyutilizing a network of mobile and/or static nodes. As a non-limitingexample, various aspects of this disclosure provide communicationnetwork architectures, systems, and methods for supporting a dynamicallyconfigurable communication network comprising a complex array of bothstatic and moving communication nodes (e.g., the Internet of movingthings, autonomous vehicle networks, etc.). For example, a communicationnetwork implemented in accordance with various aspects of the presentdisclosure may operate in one of a plurality of modalities comprisingvarious fixed nodes, mobile nodes, and/or a combination thereof, whichare selectable to achieve any of a variety of system goals. In exampleimplementation in accordance with the present disclosure, suchcommunication network may be configured to support adaptive managementof antennas used in the network.

DETAILED DESCRIPTION OF VARIOUS ASPECTS OF THE DISCLOSURE

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e., hardware) and any software and/orfirmware (“code”) that may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory (e.g., a volatileor non-volatile memory device, a general computer-readable medium, etc.)may comprise a first “circuit” when executing a first one or more linesof code and may comprise a second “circuit” when executing a second oneor more lines of code. Additionally, a circuit may comprise analogand/or digital circuitry. Such circuitry may, for example, operate onanalog and/or digital signals. It should be understood that a circuitmay be in a single device or chip, on a single motherboard, in a singlechassis, in a plurality of enclosures at a single geographical location,in a plurality of enclosures distributed over a plurality ofgeographical locations, etc. Similarly, the term “module” may, forexample, refer to a physical electronic components (i.e., hardware) andany software and/or firmware (“code”) that may configure the hardware,be executed by the hardware, and or otherwise be associated with thehardware.

As utilized herein, circuitry is “operable” to perform a functionwhenever the circuitry comprises the necessary hardware and code (if anyis necessary) to perform the function, regardless of whether performanceof the function is disabled, or not enabled (e.g., by auser-configurable setting, factory setting or trim, etc.).

As utilized herein, “and/or” means any one or more of the items in thelist joined by “and/or”. As an example, “x and/or y” means any elementof the three-element set {(x), (y), (x, y)}. That is, “x and/or y” means“one or both of x and y.” As another example, “x, y, and/or z” means anyelement of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z),(x, y, z)}. That is, “x, y, and/or z” means “one or more of x, y, andz.” As utilized herein, the terms “e.g.,” and “for example,”“exemplary,” and the like set off lists of one or more non-limitingexamples, instances, or illustrations.

The terminology used herein is for the purpose of describing particularexamples only and is not intended to be limiting of the disclosure. Asused herein, the singular forms are intended to include the plural formsas well, unless the context clearly indicates otherwise. It will befurther understood that the terms “comprises,” “includes,” “comprising,”“including,” “has,” “have,” “having,” and the like when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another element. Thus, for example, a first element, afirst component or a first section discussed below could be termed asecond element, a second component or a second section without departingfrom the teachings of the present disclosure. Similarly, various spatialterms, such as “upper,” “lower,” “side,” and the like, may be used indistinguishing one element from another element in a relative manner. Itshould be understood, however, that components may be oriented indifferent manners, for example an electronic device may be turnedsideways so that its “top” surface is facing horizontally and its “side”surface is facing vertically, without departing from the teachings ofthe present disclosure.

With the proliferation of the mobile and/or static things (e.g.,devices, machines, people, etc.) and logistics for such things to becomeconnected to each other (e.g., in the contexts of smart logistics,transportation, environmental sensing, etc.), a platform that is forexample always-on, robust, scalable and secure that is capable ofproviding connectivity, services and Internet access to such things (orobjects), anywhere and anytime is desirable. Efficient power utilizationwithin the various components of such system is also desirable.

Accordingly, various aspects of the present disclosure provide afully-operable, always-on, responsive, robust, scalable, secureplatform/system/architecture to provide connectivity, services andInternet access to all mobile things and/or static things (e.g.,devices, machines, people, access points, end user devices, sensors,etc.) anywhere and anytime, while operating in an energy-efficientmanner.

Various aspects of the present disclosure provide a platform that isflexibly configurable and adaptable to the various requirements,features, and needs of different environments, where each environmentmay be characterized by a respective level of mobility and density ofmobile and/or static things, and the number and/or types of access tothose things. Characteristics of various environments may, for example,include high mobility of nodes (e.g., causing contacts or connections tobe volatile), high number of neighbors, high number of connected mobileusers, mobile access points, availability of multiple networks andtechnologies (e.g., sometimes within a same area), etc. For example, themode of operation of the platform may be flexibly adapted fromenvironment to environment, based on each environment's respectiverequirements and needs, which may be different from other environments.Additionally for example, the platform may be flexibly optimized (e.g.,at design/installation time and/or in real-time) for different purposes(e.g., to reduce the latency, increase throughput, reduce powerconsumption, load balance, increase reliability, make more robust withregard to failures or other disturbances, etc.), for example based onthe content, service or data that the platform provides or handleswithin a particular environment.

In accordance with various aspects of the present disclosure, manycontrol and management services (e.g., mobility, security, routing,etc.) are provided on top of the platform (e.g., directly, using controloverlays, using containers, etc.), such services being compatible withthe services currently deployed on top of the Internet or othercommunication network(s).

The communication network (or platform), in whole or in part, may forexample be operated in public and/or private modes of operation, forexample depending on the use case. The platform may, for example,operate in a public or private mode of operation, depending on theuse-case (e.g., public Internet access, municipal environment sensing,fleet operation, etc.).

Additionally for example, in an implementation in which various networkcomponents are mobile, the transportation and/or signal controlmechanisms may be adapted to serve the needs of the particularimplementation. Also for example, wireless transmission power and/orrate may be adapted (e.g., to mitigate interference, to reduce powerconsumption, to extend the life of network components, etc.

Various example implementations of a platform, in accordance withvarious aspects of the present disclosure, are capable of connectingdifferent subsystems, even when various other subsystems that maynormally be utilized are unavailable. For example, the platform maycomprise various built-in redundancies and fail-recovery mechanisms. Forexample, the platform may comprise a self-healing capability,self-configuration capability, self-adaptation capability, etc. Theprotocols and functions of the platform may, for example, be prepared tobe autonomously and smoothly configured and adapted to the requirementsand features of different environments characterized by different levelsof mobility and density of things (or objects), the number/types ofaccess to those things. For example, various aspects of the platform maygather context parameters that can influence any or all decisions. Suchparameters may, for example, be derived locally, gathered from aneighborhood, fixed APs, the Cloud, etc. Various aspects of the platformmay also, for example, ask for historical information to feed any of thedecisions, where such information can be derived from historical data,from surveys, from simulators, etc. Various aspects of the platform mayadditionally, for example, probe or monitor decisions made throughoutthe network, for example to evaluate the network and/or the decisionsthemselves in real-time. Various aspects of the platform may further,for example, enforce the decisions in the network (e.g., afterevaluating the probing results). Various aspects of the platform may,for example, establish thresholds to avoid any decision that is to beconstantly or repeatedly performed without any significant advantage(e.g., technology change, certificate change, IP change, etc.). Variousaspects of the platform may also, for example, learn locally (e.g., withthe decisions performed) and dynamically update the decisions.

In addition to (or instead of) failure robustness, a platform mayutilize multiple connections (or pathways) that exist between distinctsub-systems or elements within the same sub-system, to increase therobustness and/or load-balancing of the system.

The following discussion will present examples of the functionalityperformed by various example subsystems of the communication network. Itshould be understood that the example functionality discussed hereinneed not be performed by the particular example subsystem or by a singlesubsystem. For example, the subsystems present herein may interact witheach other, and data or control services may be deployed either in acentralized way, or having their functionalities distributed among thedifferent subsystems, for example leveraging the cooperation between theelements of each subsystem.

Various aspects of the present disclosure provide a communicationnetwork (e.g., a city-wide vehicular network, a shipping port-sizedvehicular network, a campus-wide vehicular network, etc.) that utilizesvehicles (e.g., automobiles, buses, trucks, boats, forklifts,human-operated vehicles, autonomous and/or remote controlled vehicles,etc.) as Wi-Fi hotspots. Note that Wi-Fi is generally used throughoutthis discussion as an example, but the scope of various aspects of thisdisclosure is not limited thereto. For example, other wireless LANtechnologies, PAN technologies, MAN technologies, etc., may be utilized.Such utilization may, for example, provide cost-effective ways to gathersubstantial amounts of urban data, and provide for the efficientoffloading of traffic from congested cellular networks (or othernetworks). In controlled areas (e.g., ports, harbors, etc.) with manyvehicles, a communication network in accordance with various aspects ofthis disclosure may expand the wireless coverage of existing enterpriseWi-Fi networks, for example providing for real-time communication withvehicle drivers (e.g., human, computer-controlled, etc.) and othermobile employees without the need for SIM cards or cellular (or othernetwork) data plans.

Vehicles may have many advantageous characteristics that make themuseful as Wi-Fi (or general wireless) hotspots. For example, vehiclesgenerally have at least one battery, vehicles are generally denselyspread over the city at street level and/or they are able to establishmany contacts with each other in a controlled space, and vehicles cancommunicate with 10 x the range of normal Wi-Fi in the 5.9 GHz frequencyband, reserved for intelligent transportation systems in the EU, theU.S., and elsewhere. Note that the scope of this disclosure is notlimited to such 5.9 GHz wireless communication. Further, vehicles areable to effectively expand their coverage area into a swath over aperiod of time, enabling a single vehicle access point to interact withsubstantially more data sources over the period of time.

In accordance with various aspects of the present disclosure, anaffordable multi-network on-board unit (OBU) is presented. Note that theOBU may also be referred to herein as a mobile access point, Mobile AP,MAP, etc. The OBU may, for example, comprise a plurality of networkinginterfaces (e.g., Wi-Fi, 802.11p, 4G, Bluetooth, UWB, etc.). The OBUmay, for example, be readily installed in or on private and/or publicvehicles (e.g., individual user vehicles, vehicles of private fleets,vehicles of public fleets, etc.). The OBU may, for example, be installedin transportation fleets, waste management fleets, law enforcementfleets, emergency services, road maintenance fleets, taxi fleets,aircraft fleets, etc. The OBU may, for example, be installed in or on avehicle or other structure with free mobility or relatively limitedmobility. The OBU may also, for example, be carried by a person orservice animal, mounted to a bicycle, mounted to a moving machine ingeneral, mounted to a container, etc.

The OBUs may, for example, operate to connect passing vehicles to thewired infrastructure of one or more network providers, telecomoperators, etc. In accordance with the architecture, hardware, andsoftware functionality discussed herein, vehicles and fleets can beconnected not just to the cellular networks (or other wide area ormetropolitan area networks, etc.) and existing Wi-Fi hotspots spreadover a city or a controlled space, but also to other vehicles (e.g.,utilizing multi-hop communications to a wired infrastructure, single ormulti-hop peer-to-peer vehicle communication, etc.). The vehicles and/orfleets may, for example, form an overall mesh of communication links,for example including the OBUs and also fixed Access Points (APs)connected to the wired infrastructure (e.g., a local infrastructure,etc.). Note that OBUs herein may also be referred to as “Mobile APs,”“mobile hotspots,” “MAPs,” etc. Also note that fixed access points mayalso be referred to herein as Road Side Units (RSUs), Fixed APs, FAPs,etc.

In an example implementation, the OBUs may communicate with the FixedAPs utilizing a relatively long-range protocol (e.g., 802.11p, etc.),and the Fixed APs may, in turn, be hard wired to the wiredinfrastructure (e.g., via cable, tethered optical link, etc.). Note thatFixed APs may also, or alternatively, be coupled to the infrastructurevia wireless link (e.g., 802.11p, etc.). Additionally, clients or userdevices may communicate with the OBUs using one or more relativelyshort-range protocols (e.g., Wi-Fi, Bluetooth, UWB, etc.). The OBUs, forexample having a longer effective wireless communication range thantypical Wi-Fi access points or other wireless LAN/PAN access points(e.g., at least for links such as those based on 802.11p, etc.), arecapable of substantially greater coverage areas than typical Wi-Fi orother wireless LAN/PAN access points, and thus fewer OBUs are necessaryto provide blanket coverage over a geographical area.

The OBU may, for example, comprise a robust vehicular networking module(e.g., a connection manager) which builds on long-range communicationprotocol capability (e.g., 802.11p, etc.). For example, in addition tocomprising 802.11p (or other long-range protocol) capability tocommunicate with Fixed APs, vehicles, and other nodes in the network,the OBU may comprise a network interface (e.g., 802.11a/b/g/n, 802.11ac,802.11af, any combination thereof, etc.) to provide wireless local areanetwork (WLAN) connectivity to end user devices, sensors, fixed Wi-Fiaccess points, etc. For example, the OBU may operate to providein-vehicle Wi-Fi Internet access to users in and/or around the vehicle(e.g., a bus, train car, taxi cab, public works vehicle, etc.). The OBUmay further comprise one or more wireless backbone communicationinterfaces (e.g., cellular network interfaces, etc.). Though in variousexample scenarios, a cellular network interface (or other wirelessbackbone communication interface) might not be the preferred interfacefor various reasons (e.g., cost, power, bandwidth, etc.), the cellularnetwork interface may be utilized to provide connectivity ingeographical areas that are not presently supported by a Fixed AP, maybe utilized to provide a fail-over communication link, may be utilizedfor emergency communications, may be utilized to subscribe to localinfrastructure access, etc. The cellular network interface may also, forexample, be utilized to allow the deployment of solutions that aredependent on the cellular network operators.

An OBU, in accordance with various aspects of the present disclosure,may for example comprise a smart connection manager that can select thebest available wireless link(s) (e.g., Wi-Fi, 802.11p, cellular, vehiclemesh, etc.) with which to access the Internet. The OBU may also, forexample, provide geo-location capabilities (e.g., GPS, etc.), motiondetection sensors to determine if the vehicle is in motion, and a powercontrol subsystem (e.g., to ensure that the OBU does not deplete thevehicle battery, etc.). The OBU may, for example, comprise any or all ofthe sensors (e.g., environmental sensors, etc.) discussed herein.

The OBU may also, for example, comprise a manager that managesmachine-to-machine data acquisition and transfer (e.g., in a real-timeor delay-tolerant fashion) to and from the cloud. For example, the OBUmay log and/or communicate information of the vehicles.

The OBU may, for example, comprise a connection and/or routing managerthat operates to perform routing of communications in avehicle-to-vehicle/vehicle-to-infrastructure multi-hop communication. Amobility manager (or controller, MC) may, for example, ensure thatcommunication sessions persist over one or more handoff(s) (alsoreferred to herein as a “handover” or “handovers”) (e.g., betweendifferent Mobile APs, Fixed APs, base stations, hot spots, etc.), amongdifferent technologies (e.g., 802.11p, cellular, Wi-Fi, satellite,etc.), among different MCs (e.g., in a fail-over scenario, loadredistribution scenario, etc.), across different interfaces (or ports),etc. Note that the MC may also be referred to herein as a Local MobilityAnchor (LMA), a Network Controller, etc. Note that the MC, or aplurality thereof, may for example be implemented as part of thebackbone, but may also, or alternatively, be implemented as part of anyof a variety of components or combinations thereof. For example, the MCmay be implemented in a Fixed AP (or distributed system thereof), aspart of an OBU (or a distributed system thereof), etc. Variousnon-limiting examples of system components and/or methods are providedin U.S. Provisional Application No. 62/222,098, filed Sep. 22, 2015, andtitled “Systems and Method for Managing Mobility in a Network of MovingThings,” the entire contents of which are hereby incorporated herein byreference. Note that in an example implementation including a pluralityof MCs, such MCs may be co-located and/or may be geographicallydistributed.

Various aspects of the present disclosure also provide a cloud-basedservice-oriented architecture that handles the real-time management,monitoring and reporting of the network and clients, the functionalitiesrequired for data storage, processing and management, the Wi-Fi clientauthentication and Captive Portal display, etc.

A communication network (or component thereof) in accordance withvarious aspects of the present disclosure may, for example, support awide range of smart city applications (or controlled scenarios, orconnected scenarios, etc.) and/or use-cases, as described herein.

For example, an example implementation may operate to turn each vehicle(e.g., both public and private taxis, buses, trucks, etc.) into a MobileAP (e.g., a mobile Wi-Fi hotspot), offering Internet access toemployees, passengers and mobile users travelling in the city, waitingin bus stops, sitting in parks, etc. Moreover, through an examplevehicular mesh network formed between vehicles and/or fleets ofvehicles, an implementation may be operable to offload cellular trafficthrough the mobile Wi-Fi hotspots and/or fixed APs (e.g., 802.11p-basedAPs) spread over the city and connected to the wired infrastructure ofpublic or private telecom operators in strategic places, while ensuringthe widest possible coverage at the lowest possible cost.

An example implementation (e.g., of a communication network and/orcomponents thereof) may, for example, be operable as a massive urbanscanner that gathers large amounts of data (e.g., continuously)on-the-move, actionable or not, generated by a myriad of sourcesspanning from the in-vehicle sensors or On Board Diagnostic System port(e.g., OBD2, etc.), interface with an autonomous vehicle driving system,external Wi-Fi/Bluetooth-enabled sensing units spread over the city,devices of vehicles' drivers and passengers (e.g., informationcharacterizing such devices and/or passengers, etc.), positioning systemdevices (e.g., position information, velocity information, trajectoryinformation, travel history information, etc.), etc.

Depending on the use case, the OBU may for example process (or computer,transform, manipulate, aggregate, summarize, etc.) the data beforesending the data from the vehicle, for example providing the appropriategranularity (e.g., value resolution) and sampling rates (e.g., temporalresolution) for each individual application. For example, the OBU may,for example, process the data in any manner deemed advantageous by thesystem. The OBU may, for example, send the collected data (e.g., rawdata, preprocessed data, information of metrics calculated based on thecollected data, etc.) to the Cloud (e.g., to one or more networkedservers coupled to any portion of the network) in an efficient andreliable manner to improve the efficiency, environmental impact andsocial value of municipal city operations and transportation services.Various example use cases are described herein.

In an example scenario in which public buses are moving along cityroutes and/or taxis are performing their private transportationservices, the OBU is able to collect large quantities of real-time datafrom the positioning systems (e.g., GPS, etc.), from accelerometermodules, etc. The OBU may then, for example, communicate such data tothe Cloud, where the data may be processed, reported and viewed, forexample to support such public or private bus and/or taxi operations,for example supporting efficient remote monitoring and scheduling ofbuses and taxis, respectively.

In an example implementation, small cameras (or other sensors) may becoupled to small single-board computers (SBCs) that are placed above thedoors of public buses to allow capturing image sequences of peopleentering and leaving buses, and/or on stops along the bus routes inorder to estimate the number of people waiting for a bus. Such data maybe gathered by the OBU in order to be sent to the Cloud. With such data,public transportation systems may detect peaks; overcrowded buses,routes and stops; underutilized buses, routes and stops; etc., enablingaction to be taken in real-time (e.g., reducing bus periodicity todecrease fuel costs and CO₂ emissions where and when passenger flows aresmaller, etc.) as well as detecting systematic transportation problems.

An OBU may, for example, be operable to communicate with any of avariety of Wi-Fi-enabled sensor devices equipped with a heterogeneouscollection of environmental sensors. Such sensors may, for example,comprise noise sensors (microphones, etc.), gas sensors (e.g., sensingCO, NO₂, O₃, volatile organic compounds (or VOCs), CO₂, etc.), smokesensors, pollution sensors, meteorological sensors (e.g., sensingtemperature, humidity, luminosity, particles, solar radiation, windspeed (e.g., anemometer), wind direction, rain (e.g., a pluviometer),optical scanners, biometric scanners, cameras, microphones, etc.). Suchsensors may also comprise sensors associated with users (e.g., vehicleoperators or passengers, passersby, etc.) and/or their personal devices(e.g., smart phones or watches, biometrics sensors, wearable sensors,implanted sensors, etc.). Such sensors may, for example, comprisesensors and/or systems associated with on-board diagnostic (OBD) unitsfor vehicles, autonomous vehicle driving systems, etc. Such sensors may,for example, comprise positioning sensors (e.g., GPS sensors, Galileosensors, GLONASS sensors, etc.). Note that such positioning sensors maybe part of a vehicle's operational system (e.g., a localhuman-controlled vehicle, an autonomous vehicle, a remotehuman-controlled vehicle, etc.) Such sensors may, for example, comprisecontainer sensors (e.g., garbage can sensors, shipping containersensors, container environmental sensors, container tracking sensors,etc.).

Once a vehicle enters the vicinity of such a sensor device, a wirelesslink may be established, so that the vehicle (or OBU thereof) cancollect sensor data from the sensor device and upload the collected datato a database in the Cloud. The appropriate action can then be taken. Inan example waste management implementation, several waste management (orcollection) trucks may be equipped with OBUs that are able toperiodically communicate with sensors installed on containers in orderto gather information about waste level, time passed since lastcollection, etc. Such information may then sent to the Cloud (e.g., to awaste management application coupled to the Internet, etc.) through thevehicular mesh network, in order to improve the scheduling and/orrouting of waste management trucks. Note that various sensors may alwaysbe in range of the Mobile AP (e.g., vehicle-mounted sensors). Note thatthe sensor may also (or alternatively) be mobile (e.g., a sensor mountedto another vehicle passing by a Mobile AP or Fixed AP, a drone-mountedsensor, a pedestrian-mounted sensor, etc.).

In an example implementation, for example in a controlled space (e.g., aport, harbor, airport, factory, plantation, mine, etc.) with manyvehicles, machines and employees, a communication network in accordancewith various aspects of the present disclosure may expand the wirelesscoverage of enterprise and/or local Wi-Fi networks, for example withoutresorting to a Telco-dependent solution based on SIM cards or cellularfees. In such an example scenario, apart from avoiding expensivecellular data plans, limited data rate and poor cellular coverage insome places, a communication network in accordance with various aspectsof the present disclosure is also able to collect and/or communicatelarge amounts of data, in a reliable and real-time manner, where suchdata may be used to optimize harbor logistics, transportationoperations, etc.

For example in a port and/or harbor implementation, by gatheringreal-time information on the position, speed, fuel consumption and CO₂emissions of the vehicles, the communication network allows a portoperator to improve the coordination of the ship loading processes andincrease the throughput of the harbor. Also for example, thecommunication network enables remote monitoring of drivers' behaviors,behaviors of autonomous vehicles and/or control systems thereof, trucks'positions and engines' status, and then be able to provide real-timenotifications to drivers (e.g., to turn on/off the engine, follow theright route inside the harbor, take a break, etc.), for example humandrivers and/or automated vehicle driving systems, thus reducing thenumber and duration of the harbor services and trips. Harbor authoritiesmay, for example, quickly detect malfunctioning trucks and abnormaltrucks' circulation, thus avoiding accidents in order to increase harborefficiency, security, and safety. Additionally, the vehicles can alsoconnect to Wi-Fi access points from harbor local operators, and provideWi-Fi Internet access to vehicles' occupants and surrounding harboremployees, for example allowing pilots to save time by filing reportsvia the Internet while still on the water.

Various implementations in accordance with the present disclosure aredirected to managing antennas in communication networks comprisingstatic and moving communication nodes (e.g., the Internet of movingthings, autonomous vehicle networks, etc.). An example method, inaccordance with the present disclosure, may comprise managing antennasin a vehicle communication network comprising one or more mobile accesspoints (MAPs) and one or more fixed access points (FAPs). The managingmay comprise selecting an initial antenna setup comprising, for eachnode in the vehicle communication network, corresponding to one of theone or more MAPs and the one or more FAPs, a corresponding initial nodeantenna arrangement associated with the node; obtaining informationrelating to the vehicle communication network and/or operations of thevehicle communication network; determining based on the obtainedinformation if a change to the initial antenna setup is required; andwhen a change is required: identifying one or more particular nodeantenna arrangements that are to be modified; determining for eachidentified node antenna arrangement, one or more correspondingadjustments; and applying the determined adjustments.

In an example implementation, the method may comprise selecting theinitial antenna setup based on previously obtained and/or pre-definedinformation associated with deployment and/or operation of vehiclecommunication networks.

In an example implementation, the method may comprise determining theinitial node antenna arrangement and/or the adjustments, for each node,based on characteristics associated with installation of the node. Thecharacteristics may comprise, when the node may comprise a fixed accesspoint (FAP), physical characteristics associated with a location wherethe FAB is installed.

In an example implementation, each node antenna arrangement may comprisesetting of a number of antennas used for that node antenna arrangement.

In an example implementation, each node antenna arrangement maycomprise, for each antenna, a type selection; with the type selectioncomprising selection of one of an omnidirectional antenna, a sectorantenna, or a directional antenna.

In an example implementation, each node antenna arrangement maycomprise, for each antenna, a positioning selection; with thepositioning selection comprising selection of one of an internal antennaor an external antenna.

In an example implementation, each node antenna arrangement maycomprise, for each antenna, one or more configuration parameters; withthe one or more configuration parameters relating to one or more ofgain, range, throughput, delay, and error performance.

In an example implementation, the initial antenna setup may beconfigured to optimize performance, based on one or more factorscomprising: reducing number of sites for fixed access point (FAP)installation, reducing installation time for each node, increasingoverall network coverage, increasing coverage for high traffic areas,and reducing maintenance delays and cost.

An example system, in accordance with the present disclosure, configuredfor implementing an antenna management scheme in a vehicle communicationnetwork comprising one or more mobile access points (MAPs) and one ormore fixed access points (FAPs), may comprise one or more communicationcircuits configured for communication of signals for transmission andreception of data; one or more storage circuits configured for storingof instructions and data; and at least one processing circuit. The atleast one processing circuit may be operable to select an initialantenna setup comprising, for each node in the vehicle communicationnetwork, corresponding to one of the one or more MAPs and the one ormore FAPs, a corresponding initial node antenna arrangement associatedwith the node. The one or more communication circuits are operable toreceive information relating to the vehicle communication network and/oroperations of the vehicle communication network, and the at least oneprocessing circuit may be operable process the obtained information anddetermine, based on the processing, if a change to the initial antennasetup is required. When a change is required, the at least oneprocessing circuit may be operable to: identify one or more particularnode antenna arrangements that are to be modified, determine for eachidentified node antenna arrangement, one or more correspondingadjustments, and generate instructions or control data for applying thedetermined adjustments.

In an example implementation, the at least one processing circuit may beoperable to select the initial antenna setup based on previouslyobtained and/or pre-defined information associated with deploymentand/or operation of vehicle communication networks.

In an example implementation, the at least one processing circuit may beoperable to determine the initial node antenna arrangement and/or theadjustments, for each node, based on characteristics associated withinstallation of the node. The characteristics may comprise, when thenode may comprise a fixed access point (FAP), physical characteristicsassociated with a location where the FAB is installed.

In an example implementation, each node antenna arrangement may comprisesetting of a number of antennas used for the node antenna arrangement.

In an example implementation, each node antenna arrangement maycomprise, for each antenna, a type selection; with the type selectioncomprising selection of one from an omnidirectional antenna, a sectorantenna, or a directional antenna.

In an example implementation, each node antenna arrangement maycomprise, for each antenna, a positioning selection; with thepositioning selection comprising selection of one of an internal antennaor an external antenna.

In an example implementation, each node antenna arrangement maycomprise, for each antenna, one or more configuration parameters; withthe one or more configuration parameters relating to one or more ofgain, range, throughput, delay, and error performance.

In an example implementation, the initial antenna setup is configured tooptimize performance, based on one or more factors comprising: reducingnumber of sites for fixed access point (FAP) installation, reducinginstallation time for each node, increasing overall network coverage,increasing coverage for high traffic areas, and reducing maintenancedelays and cost.

An example non-transitory machine-readable storage, in accordance withthe present disclosure, may have stored thereon a computer programcomprising at least one code section comprising a plurality ofinstructions executable by a machine comprising at least one processor,to cause the machine to manage antennas in a vehicle communicationnetwork by performing a plurality of steps. The vehicle communicationnetwork may comprise one or more mobile access points (MAPs) and one ormore fixed access points (FAPs). The plurality of steps may comprise:selecting an initial antenna setup comprising, for each node in thevehicle communication network, corresponding to one of the one or moreMAPs and the one or more FAPs, a corresponding initial node antennaarrangement associated with the node; obtaining information relating tothe vehicle communication network and/or operations of the vehiclecommunication network; determining based on the obtained information ifa change to the initial antenna setup is required; and when a change isrequired: identifying one or more particular node antenna arrangementsthat are to be modified; determining for each identified node antennaarrangement, one or more corresponding adjustments; and applying thedetermined adjustments.

In an example implementation, the plurality of steps may furthercomprise selecting the initial antenna setup based on previouslyobtained and/or pre-defined information associated with deploymentand/or operation of vehicle communication networks.

In an example implementation, the plurality of steps may furthercomprise determining the initial node antenna arrangement and/or theadjustments, for each node, based on characteristics associated withinstallation of the node.

The characteristics may comprise, when the node may comprise a fixedaccess point (FAP), physical characteristics associated with a locationwhere the FAB is installed.

In an example implementation, each node antenna arrangement may comprisesetting of a number of antennas used for the node antenna arrangement.

In an example implementation, each node antenna arrangement maycomprise, for each antenna, a type selection; with the type selectioncomprising selection of one of an omnidirectional antenna, a sectorantenna, or a directional antenna.

In an example implementation, each node antenna arrangement maycomprise, for each antenna, a positioning selection; with thepositioning selection comprising selection of one of an internal antennaor an external antenna.

In an example implementation, each node antenna arrangement maycomprise, for each antenna, one or more configuration parameters; withthe one or more configuration parameters relating to one or more ofgain, range, throughput, delay, and error performance.

In an example implementation, the initial antenna setup is configured tooptimize performance, based on one or more factors comprising: reducingnumber of sites for fixed access point (FAP) installation, reducinginstallation time for each node, increasing overall network coverage,increasing coverage for high traffic areas, and reducing maintenancedelays and cost.

FIG. 1 shows a block diagram of a communication network 100, inaccordance with various aspects of this disclosure. Any or all of thefunctionality discussed herein may be performed by any or all of theexample components of the example network 100. Also, the example network100 (and/or network components) may, for example, share any or allcharacteristics with the other example networks (and/or networkcomponents) 200, 300, 400, 500-570, and 600, discussed herein.

The example network 100, for example, comprises a Cloud that may, forexample comprise any of a variety of network level components. The Cloudmay, for example, comprise any of a variety of server systems executingapplications that monitor and/or control components of the network 100.Such applications may also, for example, manage the collection ofinformation from any of a large array of networked information sources,many examples of which are discussed herein. The Cloud (or a portionthereof) may also be referred to, at times, as an API. For example,Cloud (or a portion thereof) may provide one or more applicationprogramming interfaces (APIs) which other devices may use forcommunicating/interacting with the Cloud.

An example component of the Cloud may, for example, manageinteroperability with various multi-cloud systems and architectures.Another example component (e.g., a Cloud service component) may, forexample, provide various cloud services (e.g., captive portal services,authentication, authorization, and accounting (AAA) services, APIGateway services, etc.). An additional example component (e.g., aDevCenter component) may, for example, provide network monitoring and/ormanagement functionality, manage the implementation of software updates,etc. A further example component of the Cloud may manage data storage,data analytics, data access, etc. A still further example component ofthe Cloud may include any of a variety of third-partly applications andservices.

The Cloud may, for example, be coupled to the Backbone/CoreInfrastructure of the example network 100 via the Internet (e.g.,utilizing one or more Internet Service Providers). Though the Internetis provided by example, it should be understood that scope of thepresent disclosure is not limited thereto.

The Backbone/Core may, for example, comprise any one or more differentcommunication infrastructure components. For example, one or moreproviders may provide backbone networks or various components thereof.As shown in the example network 100 illustrated in FIG. 1, a Backboneprovider may provide wireline access (e.g., PSTN, fiber, cable, etc.).Also for example, a Backbone provider may provide wireless access (e.g.,Microwave, LTE/Cellular, 5G/TV Spectrum, etc.).

The Backbone/Core may also, for example, comprise one or more LocalInfrastructure Providers. The Backbone/Core may also, for example,comprise a private infrastructure (e.g., run by the network 100implementer, owner, etc.). The Backbone/Core may, for example, provideany of a variety of Backbone Services (e.g., AAA, Mobility, Monitoring,Addressing, Routing, Content services, Gateway Control services, etc.).

The Backbone/Core Infrastructure may comprise any of a variety ofcharacteristics, non-limiting examples of which are provided herein. Forexample, the Backbone/Core may be compatible with different wireless orwired technologies for backbone access. The Backbone/Core may also beadaptable to handle public (e.g., municipal, city, campus, etc.) and/orprivate (e.g., ports, campus, etc.) network infrastructures owned bydifferent local providers, and/or owned by the network implementer orstakeholder. The Backbone/Core may, for example, comprise and/orinterface with different Authentication, Authorization, and Accounting(AAA) mechanisms.

The Backbone/Core Infrastructure may, for example, support differentmodes of operation (e.g., L2 in port implementations, L3 in on-landpublic transportation implementations, utilizing any one or more of aplurality of different layers of digital IP networking, any combinationsthereof, equivalents thereof, etc.) or addressing pools. TheBackbone/Core may also for example, be agnostic to the Cloud provider(s)and/or Internet Service Provider(s). Additionally for example, theBackbone/Core may be agnostic to requests coming from any or allsubsystems of the network 100 (e.g., Mobile APs or OBUs (On BoardUnits), Fixed APs or RSUs (Road Side Units), MCs (Mobility Controllers)or LMAs (Local Mobility Anchors) or Network Controllers, etc.) and/orthird-party systems.

The Backbone/Core Infrastructure may, for example, comprise the abilityto utilize and/or interface with different data storage/processingsystems (e.g., MongoDB, MySql, Redis, etc.). The Backbone/CoreInfrastructure may further, for example, provide different levels ofsimultaneous access to the infrastructure, services, data, etc.

The example network 100 may also, for example, comprise a Fixed HotspotAccess Network. Various example characteristics of such a Fixed HotspotAccess Network 200 are shown at FIG. 2. The example network 200 may, forexample, share any or all characteristics with the other examplenetworks (and/or network components) 100, 300, 400, 500-570, and 600,discussed herein.

In the example network 200, the Fixed APs (e.g., the proprietary APs,the public third party APs, the private third party APs, etc.) may bedirectly connected to the local infrastructure provider and/or to thewireline/wireless backbone. Also for example, the example network 200may comprise a mesh between the various APs via wireless technologies.Note, however, that various wired technologies may also be utilizeddepending on the implementation. As shown, different fixed hotspotaccess networks can be connected to a same backbone provider, but mayalso be connected to different respective backbone providers. In anexample implementation utilizing wireless technology for backboneaccess, such an implementation may be relatively fault tolerant. Forexample, a Fixed AP may utilize wireless communications to the backbonenetwork (e.g., cellular, 3G, LTE, other wide or metropolitan areanetworks, etc.) if the backhaul infrastructure is down. Also forexample, such an implementation may provide for relatively easyinstallation (e.g., a Fixed AP with no cable power source that can beplaced virtually anywhere).

In the example network 200, the same Fixed AP can simultaneously provideaccess to multiple Fixed APs, Mobile APs (e.g., vehicle OBUs, etc.),devices, user devices, sensors, things, etc. For example, a plurality ofmobile hotspot access networks (e.g., OBU-based networks, etc.) mayutilize the same Fixed AP. Also for example, the same Fixed AP canprovide a plurality of simultaneous accesses to another single unit(e.g., another Fixed AP, Mobile AP, device, etc.), for example utilizingdifferent channels, different radios, etc.).

Note that a plurality of Fixed APs may be utilized forfault-tolerance/fail-recovery purposes. In an example implementation, aFixed AP and its fail-over AP may both be normally operational (e.g., ina same switch). Also for example, one or more Fixed APs may be placed inthe network at various locations in an inactive or monitoring mode, andready to become operational when needed (e.g., in response to a fault,in response to an emergency services need, in response to a data surge,etc.).

Referring back to FIG. 1, the example Fixed Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. Also, the example Fixed Hotspot AccessNetwork is shown with a wired communication link to one or more BackboneProviders, to the Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. The Environment may comprise any of avariety of devices (e.g., in-vehicle networks, devices, and sensors;autonomous vehicle networks, devices, and sensors; maritime (orwatercraft) and port networks, devices, and sensors; generalcontrolled-space networks, devices, and sensors; residential networks,devices, and sensors; disaster recovery & emergency networks, devices,and sensors; military and aircraft networks, devices, and sensors; smartcity networks, devices, and sensors; event (or venue) networks, devices,and sensors; underwater and underground networks, devices, and sensors;agricultural networks, devices, and sensors; tunnel (auto, subway,train, etc.) networks, devices, and sensors; parking networks, devices,and sensors; security and surveillance networks, devices, and sensors;shipping equipment and container networks, devices, and sensors;environmental control or monitoring networks, devices, and sensors;municipal networks, devices, and sensors; waste management networks,devices, and sensors, road maintenance networks, devices, and sensors,traffic management networks, devices, and sensors; advertising networks,devices and sensors; etc.).

The example network 100 of FIG. 1 also comprises a Mobile Hotspot AccessNetwork. Various example characteristics of such a Mobile Hotspot AccessNetwork 300 are shown at FIG. 3. Note that various fixed networkcomponents (e.g., Fixed APs) are also illustrated. The example network300 may, for example, share any or all characteristics with the otherexample networks (and/or network components) 100, 200, 400, 500-570, and600, discussed herein.

The example network 300 comprises a wide variety of Mobile APs (orhotspots) that provide access to user devices, provide for sensor datacollection, provide multi-hop connectivity to other Mobile APs, etc. Forexample, the example network 300 comprises vehicles from differentfleets (e.g., aerial, terrestrial, underground, (under)water, etc.). Forexample, the example network 300 comprises one or more massdistribution/transportation fleets, one or more mass passengertransportation fleets, private/public shared-user fleets, privatevehicles, urban and municipal fleets, maintenance fleets, drones,watercraft (e.g., boats, ships, speedboats, tugboats, barges, etc.),emergency fleets (e.g., police, ambulance, firefighter, etc.), etc.

The example network 300, for example, shows vehicles from differentfleets directly connected and/or mesh connected, for example using sameor different communication technologies. The example network 300 alsoshows fleets simultaneously connected to different Fixed APs, which mayor may not belong to different respective local infrastructureproviders. As a fault-tolerance mechanism, the example network 300 mayfor example comprise the utilization of long-range wirelesscommunication network (e.g., cellular, 3G, 4G, LTE, etc.) in vehicles ifthe local network infrastructure is down or otherwise unavailable. Asame vehicle (e.g., Mobile AP or OBU) can simultaneously provide accessto multiple vehicles, devices, things, etc., for example using a samecommunication technology (e.g., shared channels and/or differentrespective channels thereof) and/or using a different respectivecommunication technology for each. Also for example, a same vehicle canprovide multiple accesses to another vehicle, device, thing, etc., forexample using a same communication technology (e.g., shared channelsand/or different respective channels thereof, and/or using a differentcommunication technology).

Additionally, multiple network elements may be connected together toprovide for fault-tolerance or fail recovery, increased throughput, orto achieve any or a variety of a client's networking needs, many ofexamples of which are provided herein. For example, two Mobile APs (orOBUs) may be installed in a same vehicle, etc.

Referring back to FIG. 1, the example Mobile Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Fixed Hotspot Access Network, to one or more End UserDevice, and to the Environment (e.g., to any one of more of the sensorsor systems discussed herein, any other device or machine, etc.). Thoughthe Mobile Hotspot Access Network is not shown having a wired link tothe various other components, there may (at least at times) be such awired link, at least temporarily.

The example network 100 of FIG. 1 also comprises a set of End-UserDevices. Various example end user devices are shown at FIG. 4. Note thatvarious other network components (e.g., Fixed Hotspot Access Networks,Mobile Hotspot Access Network(s), the Backbone/Core, etc.) are alsoillustrated. The example network 400 may, for example, share any or allcharacteristics with the other example networks (and/or networkcomponents) 100, 200, 300, 500-570, and 600, discussed herein.

The example network 400 shows various mobile networked devices. Suchnetwork devices may comprise end-user devices (e.g., smartphones,tablets, smartwatches, laptop computers, webcams, personal gamingdevices, personal navigation devices, personal media devices, personalcameras, health-monitoring devices, personal location devices,monitoring panels, printers, etc.). Such networked devices may alsocomprise any of a variety of devices operating in the generalenvironment, where such devices might not for example be associated witha particular user (e.g. any or all of the sensor devices discussedherein, vehicle sensors, municipal sensors, fleet sensors road sensors,environmental sensors, security sensors, traffic sensors, waste sensors,meteorological sensors, any of a variety of different types of municipalor enterprise equipment, etc.). Any of such networked devices can beflexibly connected to distinct backbone, fixed hotspot access networks,mobile hotspot access networks, etc., using the same or differentwired/wireless technologies.

A mobile device may, for example, operate as an AP to providesimultaneous access to multiple devices/things, which may then form adhoc networks, interconnecting devices ultimately connected to distinctbackbone networks, fixed hotspot, and/or mobile hotspot access networks.Devices (e.g., any or all of the devices or network nodes discussedherein) may, for example, have redundant technologies to access distinctbackbone, fixed hotspot, and/or mobile hotspot access networks, forexample for fault-tolerance and/or load-balancing purposes (e.g.,utilizing multiple SIM cards, etc.). A device may also, for example,simultaneously access distinct backbone, fixed hotspot access networks,and/or mobile hotspot access networks, belonging to the same provider orto different respective providers. Additionally for example, a devicecan provide multiple accesses to another device/thing (e.g., viadifferent channels, radios, etc.).

Referring back to FIG. 1, the example End-User Devices are shown with awireless communication link to a backbone provider (e.g., to one or moreBackbone Providers and/or Local Infrastructure Providers), to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment. Also for example, the example End-User Devices are shownwith a wired communication link to a backbone provider, to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment.

The example network 100 illustrated in FIG. 1 has a flexiblearchitecture that is adaptable at implementation time (e.g., fordifferent use cases) and/or adaptable in real-time, for example asnetwork components enter and leave service. FIGS. 5A-5C illustrate suchflexibility by providing example modes (or configurations). The examplenetworks 500-570 may, for example, share any or all characteristics withthe other example networks (and/or network components) 100, 200, 300,400, 600, and 700, discussed herein. For example and without limitation,any or all of the communication links (e.g., wired links, wirelesslinks, etc.) shown in the example networks 500-570 are generallyanalogous to similarly positioned communication links shown in theexample network 100 of FIG. 1.

For example, various aspects of this disclosure provide communicationnetwork architectures, systems, and methods for supporting a dynamicallyconfigurable communication network comprising a complex array of bothstatic and moving communication nodes (e.g., the Internet of movingthings). For example, a communication network implemented in accordancewith various aspects of the present disclosure may operate in one of aplurality of modalities comprising various fixed nodes, mobile nodes,and/or a combination thereof, which are selectable to yield any of avariety of system goals (e.g., increased throughput, reduced latency andpacket loss, increased availability and robustness of the system, extraredundancy, increased responsiveness, increased security in thetransmission of data and/or control packets, reduced number ofconfiguration changes by incorporating smart thresholds (e.g., change oftechnology, change of certificate, change of IP, etc.), providingconnectivity in dead zones or zones with difficult access, reducing thecosts for maintenance and accessing the equipment forupdating/upgrading, etc.). At least some of such modalities may, forexample, be entirely comprised of fixed-position nodes, at leasttemporarily if not permanently.

For illustrative simplicity, many of the example aspects shown in theexample system or network 100 of FIG. 1 (and other Figures herein) areomitted from FIGS. 5A-5C, but may be present. For example, the Cloud,Internet, and ISP aspects shown in FIG. 1 and in other Figures are notexplicitly shown in FIGS. 5A-5C, but may be present in any of theexample configurations (e.g., as part of the backbone provider networkor coupled thereto, as part of the local infrastructure provider networkor coupled thereto, etc.).

For example, the first example mode 500 is presented as a normalexecution mode, for example a mode (or configuration) in which all ofthe components discussed herein are present. For example, thecommunication system in the first example mode 500 comprises a backboneprovider network, a local infrastructure provider network, a fixedhotspot access network, a mobile hotspot access network, end-userdevices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via a wired link. Note that such a wiredcoupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the first example mode 500 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Also note that in various example configurations,the backbone provider network may also be communicatively coupled to thelocal infrastructure provider network via one or more wireless (ornon-tethered) links.

Though not shown in the first example mode 500 (or any of the examplemodes of FIGS. 5A-5C), one or more servers may be communicativelycoupled to the backbone provider network and/or the local infrastructurenetwork. FIG. 1 provides an example of cloud servers beingcommunicatively coupled to the backbone provider network via theInternet.

As additionally shown in FIG. 5A, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the first example mode 500(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the fixed hotspot access network (or any componentthereof), the mobile hotspot access network (or any component thereof),the end-user devices, and/or environment devices via one or morewireless links. Note that the communication link shown in the firstexample mode 500 of FIG. 5A between the local infrastructure providernetwork and the fixed hotspot access network may be wired and/orwireless.

The fixed hotspot access network is also shown in the first example mode500 to be communicatively coupled to the mobile hotspot access network,the end-user devices, and/or environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Additionally, the mobile hotspot access network is further shownin the first example mode 500 to be communicatively coupled to theend-user devices and/or environment devices via one or more wirelesslinks. Many examples of such wireless coupling are provided herein.Further, the end-user devices are also shown in the first example mode500 to be communicatively coupled to the environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Note that in various example implementations any ofsuch wireless links may instead (or in addition) comprise a wired (ortethered) link.

In the first example mode 500 (e.g., the normal mode), information (ordata) may be communicated between an end-user device and a server (e.g.,a computer system) via the mobile hotspot access network, the fixedhotspot access network, the local infrastructure provider network,and/or the backbone provider network. As will be seen in the variousexample modes presented herein, such communication may flexibly occurbetween an end-user device and a server via any of a variety ofdifferent communication pathways, for example depending on theavailability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an end user device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network).

Similarly, in the first example mode 500 (e.g., the normal mode),information (or data) may be communicated between an environment deviceand a server via the mobile hotspot access network, the fixed hotspotaccess network, the local infrastructure provider network, and/or thebackbone provider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network and/or backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an environment device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or fixed hotspotaccess network).

As discussed herein, the example networks presented herein areadaptively configurable to operate in any of a variety of differentmodes (or configurations). Such adaptive configuration may occur atinitial installation and/or during subsequent controlled networkevolution (e.g., adding or removing any or all of the network componentsdiscussed herein, expanding or removing network capacity, adding orremoving coverage areas, adding or removing services, etc.). Suchadaptive configuration may also occur in real-time, for example inresponse to real-time changes in network conditions (e.g., networks orcomponents thereof being available or not based on vehicle oruser-device movement, network or component failure, network or componentreplacement or augmentation activity, network overloading, etc.). Thefollowing example modes are presented to illustrate characteristics ofvarious modes in which a communication system may operate in accordancewith various aspects of the present disclosure. The following examplemodes will generally be discussed in relation to the first example mode500 (e.g., the normal execution mode). Note that such example modes aremerely illustrative and not limiting.

The second example mode (or configuration) 510 (e.g., a no backboneavailable mode) may, for example, share any or all characteristics withthe first example mode 500, albeit without the backbone provider networkand communication links therewith. For example, the communication systemin the second example mode 510 comprises a local infrastructure providernetwork, a fixed hotspot access network, a mobile hotspot accessnetwork, end-user devices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the second example mode 510 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary. Also note thatin various example configurations, the local infrastructure providernetwork may also, at least temporarily, be communicatively coupled tothe mobile hotspot access network (or any component thereof) via one ormore wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the second example mode 510 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Note that the communication link(s) shown in thesecond example mode 510 of FIG. 5A between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the second examplemode 510 to be communicatively coupled to the mobile hotspot accessnetwork, the end-user devices, and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Additionally, the mobile hotspot access network isfurther shown in the second example mode 510 to be communicativelycoupled to the end-user devices and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Further, the end-user devices are also shown in thesecond example mode 510 to be communicatively coupled to the environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Note that in various exampleimplementations any of such wireless links may instead (or in addition)comprise a wired (or tethered) link.

In the second example mode 510 (e.g., the no backbone available mode),information (or data) may be communicated between an end-user device anda server (e.g., a computer, etc.) via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. As will be seen in the various example modes presentedherein, such communication may flexibly occur between an end-user deviceand a server via any of a variety of different communication pathways,for example depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the fixed hotspot access network and/or the local infrastructureprovider network (e.g., skipping the mobile hotspot access network).Also for example, information communicated between an end user deviceand a server may be communicated via the local infrastructure providernetwork (e.g., skipping the mobile hotspot access network and/or fixedhotspot access network).

Similarly, in the second example mode 510 (e.g., the no backboneavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network) via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network and/orthe local infrastructure provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thelocal infrastructure provider network (e.g., skipping the mobile hotspotaccess network and/or fixed hotspot access network).

The second example mode 510 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. Forexample, due to security and/or privacy goals, the second example mode510 may be utilized so that communication access to the public Cloudsystems, the Internet in general, etc., is not allowed. For example, allnetwork control and management functions may be within the localinfrastructure provider network (e.g., wired local network, etc.) and/orthe fixed access point network.

In an example implementation, the communication system might be totallyowned, operated and/or controlled by a local port authority. No extraexpenses associated with cellular connections need be spent. Forexample, cellular connection capability (e.g., in Mobile APs, Fixed APs,end user devices, environment devices, etc.) need not be provided. Notealso that the second example mode 510 may be utilized in a scenario inwhich the backbone provider network is normally available but iscurrently unavailable (e.g., due to server failure, due to communicationlink failure, due to power outage, due to a temporary denial of service,etc.).

The third example mode (or configuration) 520 (e.g., a no localinfrastructure and fixed hotspots available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, the fixed hotspotaccess network, and communication links therewith. For example, thecommunication system in the third example mode 520 comprises a backboneprovider network, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the third example mode 520 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the third example mode 520 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links.

The mobile hotspot access network is further shown in the third examplemode 520 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the third example mode 520 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Note that in various example implementations any of suchwireless links may instead (or in addition) comprise a wired (ortethered) link.

In the third example mode 520 (e.g., the no local infrastructure andfixed hotspots available mode), information (or data) may becommunicated between an end-user device and a server (e.g., a computer,etc.) via the mobile hotspot access network and/or the backbone providernetwork. As will be seen in the various example modes presented herein,such communication may flexibly occur between an end-user device and aserver via any of a variety of different communication pathways, forexample depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the backbone provider network (e.g., skipping the mobile hotspotaccess network).

Similarly, in the third example mode 520 (e.g., the no localinfrastructure and fixed hotspots available mode), information (or data)may be communicated between an environment device and a server via themobile hotspot access network and/or the backbone provider network. Alsofor example, an environment device may communicate with or through anend-user device (e.g., instead of or in addition to the mobile hotspotaccess network). As will be seen in the various example modes presentedherein, such communication may flexibly occur between an environmentdevice and a server (e.g., communicatively coupled to the backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the backbone provider network (e.g., skipping themobile hotspot access network).

In the third example mode 520, all control/management functions may forexample be implemented within the Cloud. For example, since the mobilehotspot access network does not have a communication link via a fixedhotspot access network, the Mobile APs may utilize a direct connection(e.g., a cellular connection) with the backbone provider network (orCloud). If a Mobile AP does not have such capability, the Mobile AP mayalso, for example, utilize data access provided by the end-user devicescommunicatively coupled thereto (e.g., leveraging the data plans of theend-user devices).

The third example mode 520 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the third example mode 520 may be utilized in anearly stage of a larger deployment, for example deployment that willgrow into another mode (e.g., the example first mode 500, example fourthmode 530, etc.) as more communication system equipment is installed.Note also that the third example mode 520 may be utilized in a scenarioin which the local infrastructure provider network and fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The fourth example mode (or configuration) 530 (e.g., a no fixedhotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thefixed hotspot access network and communication links therewith. Forexample, the communication system in the fourth example mode 530comprises a backbone provider network, a local infrastructure providernetwork, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), the end-userdevices, and/or environment devices via one or more wired links. Notethat such a wired coupling may be temporary. Also note that in variousexample configurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fourth example mode 530 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fourth example mode 530(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wired links. Note that such a wired coupling may betemporary. Also note that in various example configurations, the localinfrastructure provider network may also, at least temporarily, becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof) via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links.

The mobile hotspot access network is further shown in the fourth examplemode 530 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fourth example mode 530 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fourth example mode 530 (e.g., the no fixed hotspots mode),information (or data) may be communicated between an end-user device anda server via the mobile hotspot access network, the local infrastructureprovider network, and/or the backbone provider network. As will be seenin the various example modes presented herein, such communication mayflexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider networkand/or the backbone provider network (e.g., skipping the mobile hotspotaccess network). Also for example, information communicated between anend user device and a server may be communicated via the backboneprovider network (e.g., skipping the mobile hotspot access networkand/or local infrastructure provider network).

Similarly, in the fourth example mode 530 (e.g., the no fixed hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to themobile hotspot access network). As will be seen in the various examplemodes presented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the mobile hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or backboneprovider network).

In the fourth example mode 530, in an example implementation, some ofthe control/management functions may for example be implemented withinthe local backbone provider network (e.g., within a client premises).For example, communication to the local infrastructure provider may beperformed through the backbone provider network (or Cloud). Note that ina scenario in which there is a direct communication pathway between thelocal infrastructure provider network and the mobile hotspot accessnetwork, such communication pathway may be utilized.

For example, since the mobile hotspot access network does not have acommunication link via a fixed hotspot access network, the Mobile APsmay utilize a direct connection (e.g., a cellular connection) with thebackbone provider network (or Cloud). If a Mobile AP does not have suchcapability, the Mobile AP may also, for example, utilize data accessprovided by the end-user devices communicatively coupled thereto (e.g.,leveraging the data plans of the end-user devices).

The fourth example mode 530 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the fourth example mode 530 may be utilized inan early stage of a larger deployment, for example a deployment thatwill grow into another mode (e.g., the example first mode 500, etc.) asmore communication system equipment is installed. The fourth examplemode 530 may, for example, be utilized in a scenario in which there isno fiber (or other) connection available for Fixed APs (e.g., in amaritime scenario, in a plantation scenario, etc.), or in which a FixedAP is difficult to access or connect. For example, one or more MobileAPs of the mobile hotspot access network may be used as gateways toreach the Cloud. The fourth example mode 530 may also, for example, beutilized when a vehicle fleet and/or the Mobile APs associated therewithare owned by a first entity and the Fixed APs are owned by anotherentity, and there is no present agreement for communication between theMobile APs and the Fixed APs. Note also that the fourth example mode 530may be utilized in a scenario in which the fixed hotspot access networkis normally available but are currently unavailable (e.g., due toequipment failure, due to communication link failure, due to poweroutage, due to a temporary denial of service, etc.).

The fifth example mode (or configuration) 540 (e.g., a no mobilehotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without themobile hotspot access network and communication links therewith. Forexample, the communication system in the fifth example mode 540comprises a backbone provider network, a local infrastructure providernetwork, a fixed hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fifth example mode 540 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fifth example mode 540(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network, the fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wireless links. Note that thecommunication link(s) shown in the fifth example mode 540 of FIG. 5Bbetween the local infrastructure provider network and the fixed hotspotaccess network may be wired and/or wireless.

The fixed hotspot access network is also shown in the fifth example mode540 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fifth example mode 540 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fifth example mode 540 (e.g., the no mobile hotspots availablemode), information (or data) may be communicated between an end-userdevice and a server via the fixed hotspot access network, the localinfrastructure provider network, and/or the backbone provider network.As will be seen in the various example modes presented herein, suchcommunication may flexibly occur between an end-user device and a servervia any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc. For example, information communicated between anend user device and a server may be communicated via the localinfrastructure provider network, and/or the backbone provider network(e.g., skipping the fixed hotspot access network). Also for example,information communicated between an end user device and a server may becommunicated via the backbone provider network (e.g., skipping the fixedhotspot access network and/or local infrastructure provider network).

Similarly, in the fifth example mode 540 (e.g., the no mobile hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the fixed hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to the fixedhotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the fixedhotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the fixed hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network and/or the backboneprovider network).

In the fifth example mode 540, in an example implementation, theend-user devices and environment devices may communicate directly toFixed APs (e.g., utilizing Ethernet, Wi-Fi, etc.). Also for example, theend-user devices and/or environment devices may communicate directlywith the backbone provider network (e.g., utilizing cellularconnections, etc.).

The fifth example mode 540 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation in which end-user devices and/or environmentdevices may communicate directly with Fixed APs, such communication maybe utilized instead of Mobile AP communication. For example, the fixedhotspot access network might provide coverage for all desired areas.

Note also that the fifth example mode 540 may be utilized in a scenarioin which the fixed hotspot access network is normally available but iscurrently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The sixth example mode (or configuration) 550 (e.g., the no fixed/mobilehotspots and local infrastructure available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, fixed hotspot accessnetwork, mobile hotspot access network, and communication linkstherewith. For example, the communication system in the sixth examplemode 550 comprises a backbone provider network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the sixth example mode 550 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the sixth example mode 550 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links.

The end-user devices are also shown in the sixth example mode 550 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the sixth example mode 550 (e.g., the no fixed/mobile hotspots andlocal infrastructure available mode), information (or data) may becommunicated between an end-user device and a server via the backboneprovider network. Similarly, in the sixth example mode 550 (e.g., the nofixed/mobile hotspots and local infrastructure mode), information (ordata) may be communicated between an environment device and a server viathe backbone provider network. Also for example, an environment devicemay communicate with or through an end-user device (e.g., instead of orin addition to the mobile hotspot access network).

The sixth example mode 550 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, for example in which an end-user has not yetsubscribed to the communication system, the end-user device maysubscribe to the system through a Cloud application and by communicatingdirectly with the backbone provider network (e.g., via cellular link,etc.). The sixth example mode 550 may also, for example, be utilized inrural areas in which Mobile AP presence is sparse, Fixed AP installationis difficult or impractical, etc.

Note also that the sixth example mode 550 may be utilized in a scenarioin which the infrastructure provider network, fixed hotspot accessnetwork, and/or mobile hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The seventh example mode (or configuration) 560 (e.g., the no backboneand mobile hotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thebackbone provider network, mobile hotspot access network, andcommunication links therewith. For example, the communication system inthe seventh example mode 560 comprises a local infrastructure providernetwork, fixed hotspot access network, end-user devices, and environmentdevices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the seventh example mode 560 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the seventh example mode 560 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Note that the communication link shown inthe seventh example mode 560 of FIG. 5C between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the seventh examplemode 560 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Additionally, the end-userdevices are also shown in the seventh example mode 560 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the seventh example mode 560 (e.g., the no backbone and mobilehotspots available mode), information (or data) may be communicatedbetween an end-user device and a server via the fixed hotspot accessnetwork and/or the local infrastructure provider network. As will beseen in the various example modes presented herein, such communicationmay flexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network).

Similarly, in the seventh example mode 560 (e.g., the no backbone andmobile hotspots available mode), information (or data) may becommunicated between an environment device and a server via the fixedhotspot access network and/or the local infrastructure provider network.Also for example, an environment device may communicate with or throughan end-user device (e.g., instead of or in addition to the mobilehotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network) via any of a variety of differentcommunication pathways, for example depending on the availability of anetwork, depending on bandwidth utilization goals, depending oncommunication priority, depending on communication time (or latency)and/or reliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the local infrastructure provider network (e.g.,skipping the fixed hotspot access network).

The seventh example mode 560 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample controlled space implementation, Cloud access might not beprovided (e.g., for security reasons, privacy reasons, etc.), and full(or sufficient) coverage of the coverage area is provided by the fixedhotspot access network, and thus the mobile hotspot access network isnot needed. For example, the end-user devices and environment devicesmay communicate directly (e.g., via Ethernet, Wi-Fi, etc.) with theFixed APs.

Note also that the seventh example mode 560 may be utilized in ascenario in which the backbone provider network and/or fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The eighth example mode (or configuration) 570 (e.g., the no backbone,fixed hotspots, and local infrastructure available mode) may, forexample, share any or all characteristics with the first example mode500, albeit without the backbone provider network, local infrastructureprovider network, fixed hotspot access network, and communication linkstherewith. For example, the communication system in the eighth examplemode 570 comprises a mobile hotspot access network, end-user devices,and environment devices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the mobile hotspotaccess network is shown in the eighth example mode 570 to becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Further, the end-user devices are alsoshown in the eighth example mode 570 to be communicatively coupled tothe environment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein.

In the eighth example mode 570 (e.g., the no backbone, fixed hotspots,and local infrastructure available mode), information (or data) mightnot (at least currently) be communicated between an end-user device anda server (e.g., a coupled to the backbone provider network, localinfrastructure provider network, etc.). Similarly, information (or data)might not (at least currently) be communicated between an environmentdevice and a server (e.g., a coupled to the backbone provider network,local infrastructure provider network, etc.). Note that the environmentdevice may communicate with or through an end-user device (e.g., insteadof or in addition to the mobile hotspot access network).

The eighth example mode 570 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the eighth example mode 570 may be utilized forgathering and/or serving data (e.g., in a delay-tolerant networkingscenario), providing peer-to-peer communication through the mobilehotspot access network (e.g., between clients of a single Mobile AP,between clients of respective different Mobile APs, etc.), etc. Inanother example scenario, the eighth example mode 570 may be utilized ina scenario in which vehicle-to-vehicle communications are prioritizedabove vehicle-to-infrastructure communications. In yet another examplescenario, the eighth example mode 570 may be utilized in a scenario inwhich all infrastructure access is lost (e.g., in tunnels, parkinggarages, etc.).

Note also that the eighth example mode 570 may be utilized in a scenarioin which the backbone provider network, local infrastructure providernetwork, and/or fixed hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

As shown and discussed herein, it is beneficial to have a genericplatform that allows multi-mode communications of multiple users ormachines within different environments, using multiple devices withmultiple technologies, connected to multiple moving/static things withmultiple technologies, forming wireless (mesh) hotspot networks overdifferent environments, connected to multiple wired/wirelessinfrastructure/network backbone providers, ultimately connected to theInternet, Cloud or private network infrastructure.

FIG. 6 shows yet another block diagram of an example networkconfiguration, in accordance with various aspects of the presentdisclosure. The example network 600 may, for example, share any or allcharacteristics with the other example networks and/or networkcomponents 100, 200, 300, 400, 500-570, and 600, discussed herein.Notably, the example network 600 shows a plurality of Mobile APs (orOBUs), each communicatively coupled to a Fixed AP (or RSU), where eachMobile AP may provide network access to a vehicle network (e.g.,comprising other vehicles or vehicle networks, user devices, sensordevices, etc.).

In some instances, the availability of multiple communicationtechnologies may be used in optimizing operations of networks supportinghigh mobility, such as in networks of moving things (e.g., a vehiclenetwork, a network of or including autonomous vehicles, etc.). In thisregard, in various implementations, antennas may be adaptively managedto optimize operations and/or performance of the networks and/orparticular components thereof, as described below.

FIG. 7 shows a flow chart of an example process for automatic andself-healing management of antennas in the network of moving things, inaccordance with various aspects of the present disclosure. Shown in FIG.7 is a flow chart 700, comprising a plurality of example steps(represented as blocks 702-706), which may be performed in a suitablenetwork (e.g., one of networks 100, 200, 300, 400, etc.) to provideadaptive and intelligent antenna management scheme in a network ofmoving things.

Optimizing antennas use (e.g., placement, selection, configuration,operation, etc.) in networks of moving things may be desirable as itwould improve overall quality while reducing costs. In this regard, asdescribed (e.g., above with respect to FIGS. 1-6), the Internet ofMoving Things is supported by a infrastructure built through a meshamong fixed and mobile APs, which can establish connections with theInternet, Cloud or private networks. In order to best take advantage ofsuch networks, the connectivity between different elements in thenetwork (e.g., the mobile APs and the fixed APs available in thenetwork) may be optimized, which in turn may result in improved QoS(Quality of Service) and QoE (Quality of Experience) of the end user.

For example, by taking advantage of the vehicular mesh network built ontop of high-range wireless technology (e.g., DSRC (Dedicated Short RangeCommunications) based connections), wireless throughput may be increasedand/or latency may be reduced, thus enhancing the user QoE. In thisregard, with respect to costs, use of DSRC based connections to senddata to the Cloud is several times cheaper than doing so using thecellular network. With that in mind, for example, using the correctantennas in the right place, with the right configuration andorientation may further enhance QoS and QoE.

In step 702, initial antenna planning may be performed. This maycomprise making initial selection of sites, and for each site, makinginitial selection of antennas to be used therein. In particular, due tothe panoply of possible configurations, type of antennas (e.g.,omnidirectional antennas, directional antennas, sector antennas,different heights, different gains, outdoor/indoor, etc.), differentfrequencies (e.g., GPS, Wi-Fi, DSRC, etc.), cabling solutions (e.g.,internal or external), different sites (e.g., lampposts, traffic lights,CCTV (closed-circuit television) poles, top of buildings (e.g., on therooftops), electrified billboards and/or supports, balconies, regularstores, towers and other street furniture), every installation site isdecided/planned on a case by case decision or taking into accountprevious deployments, as well as being based on the information comingfrom surveys or using historic data already stored in the Cloud. At thesame time, it is desirable to decrease the time for each installation,but doing so with the goals of having the best coverage and bestcommunication performance (e.g., throughput, latency, packet loss,etc.), and enabling improvement of future maintenance (e.g., ensuringaccess would be easy).

In step 704, data relating to communications may be collected for eachsite (particularly insofar as related to current antenna selection,configuration, etc.), during operation after initial installation. Inthis regard, for every single site of installation, as much informationas possible may be collected, for use in preparing in advance (oroptimizing for existing site(s)) each site. In addition to informationrelating to the antennas and use thereof, other related information maybe taken into account (and thus collected), such as information relatedto the environment, the height, type of site (e.g., described before)and availability of power/network. The collected information may be usedto optimize the current site and/or may be used for making similarinstallations easier and quicker in the future.

In step 706, collected information may be processed to optimize alreadyexisting installations and/or for use in future installations. In thisregard, by taking into account the last metrics and historic data, it ispossible to quickly detect (e.g., and learn) the best configurations,polarization, orientation and, in advance, predict the best possibleinstallation and/or intervention. Doing so may result in flexibilityboth in the design time and in real-time operability, making the systemautomatically prepared to adapt remotely or schedule an intervention toperform the adaptation of any type of configuration, location,positioning, and operation mode of any antenna.

Accordingly, in various implementations in accordance with the presentdisclosure, selection and configuration of antennas may take intoaccount information obtained from previous deployments. Thus, whenmaking a deployment, a remote and a local survey of the site may betaken for the initial installation, but after the installation,pertinent information (e.g., performance related metrics) may be trackedand/or collected throughout operation of the site. For example, suchmetrics as traffic information, number of users, range of coverage,network use in particular spots, number of sessions, number of links,mean number of nodes that the AP (at the particular site) may detect ina certain perimeter, etc. may be tracked. Using an intelligent selectionand configuration algorithm, and taking into account the site ofinstallation and all the historic data of all clients, trials andtestbeds, the system may recommend particular antenna selection and/orconfiguration (e.g., installing an omnidirectional antenna instead ofdirectional, adjusting the tilt of the antenna or even suggest anotherlocation to install the AP, or change the direction, height, etc.). Forexample, an example selection and configuration algorithm may take suchinputs as historical data pertaining to a definable particular area ofinterest (e.g., a circular area, having a predefined radius around apoint that corresponds to GPS coordinates of the point where the AP orits antenna(s) is/are to be deployed or installed), defaultconfiguration based data (e.g., antenna type, direction/orientation, GPScoordinates, height, throughput, etc. for default configuration), recent(e.g., last day) metrics for site(s), etc., and may provide, based onsuch inputs, new configuration (or data pertaining thereto) as output,such as by use of logic that may comprise, for example, use of one ormore of weighted values filtering, pattern recognition, fuzzy logic,normal filters, cost functions, etc. Further, adaptations of theantennas may be triggered to reduce the need for cables, and to enableeasy installation, access and/or maintenance.

Use of such adaptive antenna management scheme may ensure takingadvantage of the fixed/mobile AP installations, while increasingtechnical performance such as range, throughput and at the same timedecrease the packet loss and delay. Further, use of the adaptive antennamanagement scheme may enable decreasing the number of APs necessary tobe installed, to cover the same area, since it is possible to have abetter coverage with less APs. Another potential benefit may beenhancement of vehicular connectivity by using the most appropriateantennas, increasing the offload percentage, coverage and throughput,and reducing interference. As part of this aspect, it may be possible toreduce, for example, a number of required components for overall systeminstallation, resulting in a more efficient implementation (e.g., acheaper project).

The adaptive antenna management scheme may be configured to account forvariations in available conditions and/or parameters pertinent to theselection, configuration, and use of antennas. For example, eachlocation may have a panoply of possible ways of installation, and/orwith particular conditions affecting installations at such locations.The fixed AP may typically be installed in, for example, lampposts,traffic lights, CCTV poles, top of buildings (on the rooftops),electrified billboards and/or supports, balconies, regular stores,towers and other street furniture, etc.

Mobile APs may be installed near the windshield of a vehicle. Further,in some cases, the use of extensors may be required, such as whereantenna installation at a particular part of the vehicle may be notfeasible of possible (e.g., inside a metal cabinet, under/inside glovebox, shelves, etc.). If we take into consideration these multiple casesand their variations, such as the make, model and type of vehicle(boats, trucks, buses, trains, light trains, etc.), we have a largenumber of possible installations. Thus, use of the adaptive antennamanagement scheme may result in a system that may be adaptable todifferent situations, maintaining the antenna gain and the expectedresults, even when the conditions are not favorable. The adaptiveantenna management scheme may also be configurable to account todifferent operational limitations or constraints.

For example, due to different local standards (e.g., in the EU, Japan,Asian, and US, for instance) each antenna must be associated to aspecific fixed AP. In this regard, each specific region may haveassociated therewith antenna related parameters, such as maximum valuesfor the antenna (gain, throughput, etc.), such as to ensure traceabilityand compliance with standards applicable in each region. Associating thevalues of the gain for each antenna to the designated fixed AP canautomatically adapt the transmission power of each AP. This can be doneby using a dedicated API compliant with the local rules. Otherparameters such as the channel to use, the use of diversity, the PSID(The Provider Service Identifier), the rate control or any otherinformation that can be customizable, can be done remotely and/orautonomously by the APs.

The adaptive antenna management scheme may allow for installation ofseveral types of antennas (e.g., omnidirectional and/ordirectional/patch antennas, and/or all-in-one), and, due to thereal-time measures and/or learning processes running at the Cloud andbeing fed by the data gathered in a specific network configuration, thesystem can quickly adapt and detect the best antennas to use. Also,using the system already described, the antennas may have a servo-motorthat can rotate them, tilt them, or even adjust the HPBW (Half-PowerBeam Width), to achieve the angular width within which antenna is mostsensitive. In some instances (e.g., in the case of ports, where theremay be constant environment changes, such as number, place andheight/stack of containers, etc.), the antennas can be adaptedautomatically, in a self-learning process.

The adaptive antenna management scheme may be configured to account fordifferent types of antenna configurations (e.g., internal vs. externalantennas, omnidirectional vs. directional antennas, use in fixed APs vs.mobile APs, etc.). In this regard, systems implemented in accordancewith the present disclosure may be customized based on the client'sneeds (e.g., for internal or external antennas), making the systems muchmore flexible to different antenna configurations.

For example, internal antennas in fixed APs (that is, antennasintegrated within the APs rather than being separate and at a distancefrom, and connected to, the APs, such as via cabling) may be used whenthe clients' needs can be met without compromising the expected andnormal results by guaranteeing the same performance as that which can beachieved with external antennas. In this regard, with internal antennas,the installation procedure of the fixed AP may be easier and use lessequipment, with the added benefit of having less visual pollution (e.g.,lots of antennas on the poles) of the AP.

Use of internal antennas for fixed APs may not be desirable in somesituations, however, such as where the only site to install theequipment is inside a building (as performance of the antennas may bedegraded, such as due to structures or parts of the building being incommunication paths, other equipment, etc.). Additionally, if theequipment must be installed too high, the antennas should be tilted inorder to increase the performance, range and bandwidth.

Use of internal antennas in mobile APs may have exactly the sameadvantages and/or may be desirable for similar reasons. In this regard,clients may also demand easy and “plug and play” installations, and withuse of internal antennas this is possible. Although, if the equipment isinstalled inside a metal cabinet, the performance may degrade. In thisregard, metal enclosures may not allow for radiation to spread, and assuch use of internal antennas may not be feasible, thus requiring use ofexternal antennas in such use scenarios. In some instances, in order tobe ready to be installed in any selected location, fixed APs haveinternal antennas ready for all interfaces (DSRC, Wi-Fi, Bluetooth,Cellular, etc.) but also have the option of using external interfaces,if necessary. One issue of having everything as internal antennas is theproper polarization of the antennas. For example, if a GPS antenna isinstalled inside and the antenna is installed in the horizontaldirection, the fixed AP should generally be installed in the horizontaldirection. If they are not so installed, the GPS signal may decrease.This may be addressed by installation of two internal antennas, to coverthe two most common polarizations (horizontal and vertical).

When using external antennas for fixed APs, extensors may be used tobetter position the antennas. These can be omnidirectional antennas,sector antennas, or unidirectional antennas. Choosing between thesedifferent types may be made on a case by case scenario in order tomaximize the range and the covered area of the antenna. In this regard,when choosing between omnidirectional and directional antennas(particularly for fixed APs), such factors as the antenna gain,direction, polarization, size and space for the installation, etc. maybe taken into consideration. Further, in some implementations, thesefactors may be weighed, such as based on the location of the antenna(e.g., in lampposts, top of buildings (on the rooftops), CCTV postsand/or supports, balconies, regular stores, towers, etc.). Further,particularly in a city, there are several other obstacles (tree foliage,advertisement signs, other antennas, buildings with differentmaterials—glass, brick, concrete, and many more) that block, reflect andinfluence the coverage of an antenna and its expected performance.

Another factor that may be considered when choosing the placement of thefixed APs and their respective antennas is the expected type ofcommunication environment—e.g., multipath and non-LoS (Line-of-Sight)environments. The installation of an omnidirectional antenna is easiersince its 360 degrees horizontal pattern supplies the coverage to alarge area around it, except in the area directly under the antenna.Therefore, one ideal place for an installation of an omnidirectionalantenna is in, for example, roundabouts in the city and in lampposts.Usually they should be installed relatively low (less than 10 meters,for example). When considering the installation of the antennas in longavenues or streets with few obstacles or on tops of buildings,directional antennas are generally better, since the signal can travelfarther distances in a particular direction.

Another type of antenna that may be used is the “all-in-one antennas.”These antennas may be ideal for installation in outdoor/indoorscenarios, and are generally easier to install since the same extensionsmay handle several antennas. Some outdoors installations, however, mayrequire adjustments to location (e.g., drilling and making new holes),and this may not be desirable. Further, the level of personalization maybe very low, depending on supply constraints.

In some instances, directional/patch Wi-Fi antennas may be used, whichmay be ideal for installations in such locations, for example, as insidea bus, to cover a long path having fiberglass and sometimes metal thatis part of the structure. In this scenario, for example, in order tocatch signals from other APs spread along cities, ports, etc.,omnidirectional antennas may be most suitable for this purpose.

With respect to the information collected and used in accordance withthe adaptive antenna management scheme (e.g., for initial deployments,subsequent adjustments at same locations, deployments at similarlocations, etc.), there may be various considerations and factors thatmay be pertinent to the configurability of the scheme. Theseconsiderations and factors may include types of information to begathered (e.g., some inputs can be static, others real-time; someupdated on a daily basis, others introduced manually; some are dependenton the way the network has to act, others are not; etc.), types ofsources (fixed APs, mobile APs, Cloud, sensors, users, networkoperators, etc.), types of tools/protocols used to gather theinformation, manner by which decisions are enforced in the network(e.g., differences between design-time configuration and real-time andscheduling an intervention), etc.

For example, in some implementations, design time configuration(pre-deployment) inputs may be used. A first type of static input maybe, for example, input from surveys done remotely and in the field(pre-deployment), which may be used as base values for the antennaselection and configuration algorithm. Another type of static input maybe input from the location of the project (e.g., power and throughputrestrictions from a country or region). These static inputs may beplaced manually, for example before the mobile APs/fixed APs aredeployed.

In some implementations real-time configuration (post-deployment) inputsmay be used. In this regard, after the deployment, an adaptive antennaselection and configuration algorithm may initiate its own survey at thelocation(s), to obtain information for achieving the optimal coverage ofa certain area. This may start first with the fixed APs, ranging theirown optimal coverage for example. After the initial surveys, dailyupdates may be used to start building historic data and then thefrequency of updates may (e.g., in each node) decay if the metricscollected get stable enough and/or may change again (increase) whendeemed necessary (e.g., if the landscape changes rapidly, and thus themetrics change abruptly, the daily updates may return or if the clientwishes to change them with instructions given from the cloud or inmobile APs with fixed routes if the route changes, etc.).

In an example use scenario, metrics collected (e.g., GPS location) maycomprise positions where certain parameters (e.g., thresholds used forQoS evaluations) are not met because of poor connections between APs andto the cloud. The collected metrics may be used in matching thelocations with the known coordinates of other APs and to increase theircoverage to match those areas. This may work for fixed APs and mobileAPs with fixed routes (e.g., bus fleet). In another example usescenario, metrics can change abruptly, such as in a city that is alwayschanging (construction, demolition, addition/removal of antennas fromother devices), and this may impact positively (or negatively) one orseveral APs (fixed and/or mobile). For example, placing a new obstacle(e.g., advertisement billboard) on top of a building or by the roadsidemay impact the coverage of the fixed and mobile APs in the surroundingarea. Therefore detection and/or compensation may be needed—e.g., todetect a lack of coverage in that general direction (which can bedetected, for example, with the lack of connection between specificnodes where connection previously occurred but no longer occurs).

The adaptive antenna management scheme may be configured to account forand/or achieve particular conditions (e.g., avoid constant changes frommodes, avoid ping-pong effect, obtain and/or use more information abouthysteresis/thresholds to smooth transitions between the different modes,probe a different mode firstly (and check if everything is acceptable),before changing, etc.). For example, in order to avoid constanttransitions in the configuration, the metrics may be collected daily,stored, and then analyzed (e.g., compared to the previous historicdata). The historic data of each node may allow for establishingexpected thresholds for that specific node and for adjusting them ifneeded. A real time adjustment of power of a mobile AP's antenna may beperformed using its own GPS location and comparing it with that of thefixed APs and other mobile APs, in an attempt to expand the area ofcoverage of the network.

In some implementations, some post analysis of the whole network may bedone on regular basis (e.g., weekly) to optimize the weaker links of thenetwork (e.g., by collecting pattern metrics of the nodes, such aschecking which nodes may lose connection to the non-cellular network,and need to go cellular, if the power of the antennas are not increased,or the opposite). In an example use scenario, adaptive emission powercontrol of the antennas may be used. For example, when too many nodesmay be present in the same spot (e.g., multiple vehicles in parkingdepot, nodes are always close together every night, etc.) the power maybe reduced on the nodes closer together to avoid competition forcoverage, only maximizing the ones that have better connections tooutside of that cluster (e.g., fixed APs, or mobile Aps that are passingby).

The adaptive antenna management scheme may be configured to supportscheduling of antenna adjustment interventions. For example, ininstances of learning/detecting that something needs to change relatedto antennas (configuration, orientation, polarization, etc.), but maynot be done remotely, the scheme may detect that need automatically andschedule an intervention.

Use of the adaptive antenna management scheme may result in significantbenefits. For example, by increasing the connectivity between fixed APsand mobile APs, their throughput/range may increase and the networklatency may decrease. Consequently, the user experience may be enhancedas result of increase in the performance throughout the region since thecoverage will be higher. The wireless vehicular network tends to havelower costs, when compared to the cellular network, and such optimizing(and ensuring the) use of the wireless vehicular network results inlower overall costs. The number of fixed APs and/or mobile APs needed tocover the same area may be reduced, thus reducing the costs.

In some instances, fixed APs and/or mobile APs may be placed in easyplaces (not necessarily the best location), but without a degradation ofthe connectivity. Since it is possible to have, in some instances,internal antennas, the cost of equipment required for supportingoperation of the network, as well as the cost of the installation of thenetwork, may be reduced, because, for example, a fewer number ofextensors and external antennas may be used and the time of installationmay be reduced. Further the added learning/self-adaptability/flexibilitymay decrease the time needed to perform each survey, decrease time ofinstallation, decrease human errors, etc. Further, optimal use of datafrom surveys/historic data may be made by feeding that data intolearning algorithms (e.g., the antenna selection and configurationalgorithm described above) which may be used to optimize the antennas'configuration, orientation, polarization, etc.

In an example implementation, a controller system may be used toimplement the adaptive antenna management scheme described herein. Inthis regard, such controller system may comprise suitable circuitry(including, e.g., one or more of general or dedicated processingcircuitry, storage circuitry, sensory circuitry, power circuitry,communication-related circuitry, etc.) for implementing and/orsupporting various functions descried in conjunction with the adaptiveantenna management scheme. For example, the controller system may beoperable to receive collected data (e.g., using the communicationcircuitry, via supported wired and/or wireless interfaces, stored thedata (e.g., in storage elements), process the data (e.g., using theprocessing circuitry, based on pre-install code stored in the storagecircuitry, for example) to determine initial antenna configurations,when and how to make adjustments to existing antenna configurations,etc. Nonetheless, the disclosure is not so limited, and in otherimplementations, functions relating to the adaptive antenna managementscheme described herein may be implemented in distributed manner—e.g.,among various existing systems and subsystems that may avail requiredresources for performing these functions.

In accordance with various aspects of this disclosure, examples of thenetworks and/or components thereof presented herein are provided in U.S.Provisional Application Ser. No. 62/222,192, titled “CommunicationNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

In accordance with various aspects of this disclosure, the networksand/or components thereof presented herein are provided with systems andmethods for integrating such networks and/or components with othernetworks and systems, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/221,997, titled “IntegratedCommunication Network for A Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for synchronizing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,016, titled “Systems and Methods forSynchronizing a Network of Moving Things,” filed on Sep. 22, 2015, whichis hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,042, titled “Systems and Methods forManaging a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for monitoring such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,066, titled “Systems and Methods forMonitoring a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for detecting and/or classifying anomalies insuch networks and/or components, non-limiting examples of which areprovided in U.S. Provisional Application Ser. No. 62/222,077, titled“Systems and Methods for Detecting and Classifying Anomalies in aNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,098, titled “Systems and Methodsfor Managing Mobility in a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing connectivity in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,121, titled “Systems and Methodsfor Managing Connectivity a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for collecting sensor data in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,135, titled “Systems and Methodsfor Collecting Sensor Data in a Network of Moving Things,” filed on Sep.22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for interfacing with such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,145, titled “Systems and Methodsfor Interfacing with a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for interfacing with a user of such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,150, titled “Systems and Methodsfor Interfacing with a User of a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for data storage and processing in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,168, titled “Systems and Methodsfor Data Storage and Processing for a Network of Moving Things,” filedon Sep. 22, 2015, which is hereby incorporated herein by reference inits entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for vehicle traffic management in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,183, titled “Systems and Methodsfor Vehicle Traffic Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for environmental management in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,186, titled “Systems and Methodsfor Environmental Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing port or shipping operation in suchnetworks and/or components, non-limiting examples of which are providedin U.S. Provisional Application Ser. No. 62/222,190, titled “Systems andMethods for Port Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of positioning orlocation information based at least in part on historical data,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/244,828, titled “Utilizing Historical Data toCorrect GPS Data in a Network of Moving Things,” filed on Oct. 22, 2015,which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of position or locationof positioning or location information based at least in part on theutilization of anchors, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/244,930, titled “Using Anchorsto Correct GPS Data in a Network of Moving Things,” filed on Oct. 22,2015, which is hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing communication between applications,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/246,368, titled “Systems and Methods forInter-Application Communication in a Network of Moving Things,” filed onOct. 26, 2015, which is hereby incorporated herein by reference in itsentirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for probing, analyzing and/or validatingcommunication, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/246,372, titled “Systems and Methodsfor Probing and Validating Communication in a Network of Moving Things,”filed on Oct. 26, 2015, which is hereby incorporated herein by referencein its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for adapting communication rate, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/250,544, titled “Adaptive Rate Control for Vehicular Networks,” filedon Nov. 4, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for reconfiguring and adapting hardware,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/273,878, titled “Systems and Methods forReconfiguring and Adapting Hardware in a Network of Moving Things,”filed on Dec. 31, 2015, which is hereby incorporated herein by referencein its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for optimizing the gathering of data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/253,249, titled “Systems and Methods for Optimizing Data Gathering ina Network of Moving Things,” filed on Nov. 10, 2015, which is herebyincorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing delay tolerant networking,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/257,421, titled “Systems and Methods for DelayTolerant Networking in a Network of Moving Things,” filed on Nov. 19,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for improving the coverage and throughput ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/265,267, titled “Systems andMethods for Improving Coverage and Throughput of Mobile Access Points ina Network of Moving Things,” filed on Dec. 9, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for coordinating channel utilization, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,858, titled “Channel Coordination in a Network of Moving Things,”filed on Dec. 22, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for implementing a network coded mesh network in thenetwork of moving things, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/257,854, titled “Systems andMethods for Network Coded Mesh Networking in a Network of MovingThings,” filed on Nov. 20, 2015, which is hereby incorporated herein byreference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for improving the coverage of fixed access points,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/260,749, titled “Systems and Methods forImproving Fixed Access Point Coverage in a Network of Moving Things,”filed on Nov. 30, 2015, which is hereby incorporated herein by referencein its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility controllers and their networkinteractions, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/273,715, titled “Systems and Methodsfor Managing Mobility Controllers and Their Network Interactions in aNetwork of Moving Things,” filed on Dec. 31, 2015, which is herebyincorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for managing and/or triggering handovers ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/281,432, titled “Systems andMethods for Managing and Triggering Handovers of Mobile Access Points ina Network of Moving Things,” filed on Jan. 21, 2016, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing captive portal-related control andmanagement, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/268,188, titled “CaptivePortal-related Control and Management in a Network of Moving Things,”filed on Dec. 16, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for extrapolating high-value data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,678, titled “Systems and Methods to Extrapolate High-Value Datafrom a Network of Moving Things,” filed on Dec. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote software updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/272,750, titled “Systems and Methodsfor Remote Software Update and Distribution in a Network of MovingThings,” filed on Dec. 30, 2015, which is hereby incorporated herein byreference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote configuration updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/278,662, titled “Systems and Methodsfor Remote Configuration Update and Distribution in a Network of MovingThings,” filed on Jan. 14, 2016, which is hereby incorporated herein byreference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for adapting the network, for exampleautomatically, based on user feedback, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,243, titled“Systems and Methods for Adapting a Network of Moving Things Based onUser Feedback,” filed on Jan. 22, 2016, which is hereby incorporatedherein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing and/or guaranteeing data integritywhen building or performing data analytics, non-limiting examples ofwhich are provided in U.S. Provisional Application Ser. No. 62/278,764,titled “Systems and Methods to Guarantee Data Integrity When BuildingData Analytics in a Network of Moving Things,” Jan. 14, 2016, which ishereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing self-initialization and/or automatedbootstrapping of mobile access points, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,515, titled“Systems and Methods for Self-Initialization and Automated Bootstrappingof Mobile Access Points in a Network of Moving Things,” filed on Jan.25, 2016, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing power supply and/or utilization,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/295,602, titled “Systems and Methods for PowerManagement in a Network of Moving Things,” filed on Feb. 16, 2016, whichis hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for automating and easing the installation and setupof the infrastructure, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/299,269, titled “Systems andMethods for Automating and Easing the Installation and Setup of theInfrastructure Supporting a Network of Moving Things,” filed on Feb. 24,2016, which is hereby incorporated herein by reference in its entirety.

In summary, various aspects of this disclosure provide communicationnetwork architectures, systems and methods for supporting a network ofmobile nodes, for example comprising a combination of mobile andstationary nodes. As a non-limiting example, various aspects of thisdisclosure provide communication network architectures, systems, andmethods for supporting a dynamically configurable communication networkcomprising a complex array of both static and moving communication nodes(e.g., the Internet of moving things). While the foregoing has beendescribed with reference to certain aspects and examples, it will beunderstood by those skilled in the art that various changes may be madeand equivalents may be substituted without departing from the scope ofthe disclosure. In addition, many modifications may be made to adapt aparticular situation or material to the teachings of the disclosurewithout departing from its scope. Therefore, it is intended that thedisclosure not be limited to the particular example(s) disclosed, butthat the disclosure will include all examples falling within the scopeof the appended claims.

What is claimed is:
 1. A method comprising: managing antennas in a vehicle communication network comprising one or more mobile access points (MAPs) and one or more fixed access points (FAPs), the managing comprising: selecting an initial antenna setup comprising, for each node in the vehicle communication network, corresponding to one of said one or more MAPs and said one or more FAPs, a corresponding initial node antenna arrangement associated with said node; obtaining information relating to said vehicle communication network and/or operations of said vehicle communication network; determining based on said obtained information if a change to said initial antenna setup is required; and when a change is required: identifying one or more particular node antenna arrangements that are to be modified; determining for each identified node antenna arrangement, one or more corresponding adjustments; and applying said determined adjustments.
 2. The method of claim 1, comprising selecting said initial antenna setup based on previously obtained and/or pre-defined information associated with deployment and/or operation of vehicle communication networks.
 3. The method of claim 1, comprising determining said initial node antenna arrangement and/or said adjustments, for each node, based on characteristics associated with installation of said node.
 4. The method of claim 3, wherein said characteristics comprise, when said node comprises a fixed access point (FAP), physical characteristics associated with a location where said FAB is installed.
 5. The method of claim 1, wherein each node antenna arrangement comprises setting of a number of antennas used for said node antenna arrangement.
 6. The method of claim 1, wherein each node antenna arrangement comprises, for each antenna, a type selection; said type selection comprising selection of one of an omnidirectional antenna, a sector antenna, or a directional antenna.
 7. The method of claim 1, wherein each node antenna arrangement comprises, for each antenna, a positioning selection; said positioning selection comprising selection of one of an internal antenna or an external antenna.
 8. The method of claim 1, wherein each node antenna arrangement comprises, for each antenna, one or more configuration parameters; said one or more configuration parameters relating to one or more of gain, range, throughput, delay, and error performance.
 9. The method of claim 1, wherein said initial antenna setup is configured to optimize performance, based on one or more factors comprising: reducing number of sites for fixed access point (FAP) installation, reducing installation time for each node, increasing overall network coverage, increasing coverage for high traffic areas, and reducing maintenance delays and cost.
 10. A system configured for implementing an antenna management scheme in a vehicle communication network comprising one or more mobile access points (MAPs) and one or more fixed access points (FAPs), the system comprising: one or more communication circuits configured for communication of signals for transmission and reception of data; one or more storage circuits configured for storing of instructions and data; and at least one processing circuit; wherein: said at least one processing circuit is operable to select an initial antenna setup comprising, for each node in the vehicle communication network, corresponding to one of said one or more MAPs and said one or more FAPs, a corresponding initial node antenna arrangement associated with said node; said one or more communication circuits are operable to receive information relating to said vehicle communication network and/or operations of said vehicle communication network; said at least one processing circuit is operable process said obtained information, and determine, based on said processing, if a change to said initial antenna setup is required; and when a change is required, said at least one processing circuit is operable to: identify one or more particular node antenna arrangements that are to be modified; determine for each identified node antenna arrangement, one or more corresponding adjustments; and generate instructions or control data for applying said determined adjustments.
 11. The system of claim 9, wherein said at least one processing circuit is operable to select said initial antenna setup based on previously obtained and/or pre-defined information associated with deployment and/or operation of vehicle communication networks.
 12. The system of claim 9, wherein said at least one processing circuit is operable to determine said initial node antenna arrangement and/or said adjustments, for each node, based on characteristics associated with installation of said node.
 13. The method of claim 12, wherein said characteristics comprise, when said node comprises a fixed access point (FAP), physical characteristics associated with a location where said FAB is installed.
 14. The system of claim 9, wherein each node antenna arrangement comprises setting of a number of antennas used for said node antenna arrangement.
 15. The system of claim 9, wherein each node antenna arrangement comprises, for each antenna, a type selection; said type selection comprising selection of one of an omnidirectional antenna, a sector antenna, or a directional antenna.
 16. The system of claim 9, wherein each node antenna arrangement comprises, for each antenna, a positioning selection; said positioning selection comprising selection of one of an internal antenna or an external antenna.
 17. The system of claim 9, wherein each node antenna arrangement comprises, for each antenna, one or more configuration parameters; said one or more configuration parameters relating to one or more of gain, range, throughput, delay, and error performance.
 18. The system of claim 9, wherein said initial antenna setup is configured to optimize performance, based on one or more factors comprising: reducing number of sites for fixed access point (FAP) installation, reducing installation time for each node, increasing overall network coverage, increasing coverage for high traffic areas, and reducing maintenance delays and cost.
 19. A non-transitory machine-readable storage stored thereon a computer program comprising at least one code section comprising a plurality of instructions executable by a machine comprising at least one processor, to cause the machine to manage antennas in a vehicle communication network comprising one or more mobile access points (MAPs) and one or more fixed access points (FAPs), by performing a plurality of steps comprising: selecting an initial antenna setup comprising, for each node in the vehicle communication network, corresponding to one of said one or more MAPs and said one or more FAPs, a corresponding initial node antenna arrangement associated with said node; obtaining information relating to said vehicle communication network and/or operations of said vehicle communication network; determining based on said obtained information if a change to said initial antenna setup is required; and when a change is required: identifying one or more particular node antenna arrangements that are to be modified; determining for each identified node antenna arrangement, one or more corresponding adjustments; and applying said determined adjustments.
 20. The non-transitory machine-readable storage of claim 19, the plurality of steps further comprising selecting said initial antenna setup based on previously obtained and/or pre-defined information associated with deployment and/or operation of vehicle communication networks.
 21. The non-transitory machine-readable storage of claim 19, the plurality of steps further determining said initial node antenna arrangement and/or said adjustments, for each node, based on characteristics associated with installation of said node.
 22. The non-transitory machine-readable storage of claim 21, wherein said characteristics comprise, when said node comprises a fixed access point (FAP), physical characteristics associated with a location where said FAB is installed.
 23. The non-transitory machine-readable storage of claim 19, wherein each node antenna arrangement comprises setting of a number of antennas used for said node antenna arrangement.
 24. The non-transitory machine-readable storage of claim 19, wherein each node antenna arrangement comprises, for each antenna, a type selection; said type selection comprising selection of one of an omnidirectional antenna, a sector antenna, or a directional antenna.
 25. The non-transitory machine-readable storage of claim 19, wherein each node antenna arrangement comprises, for each antenna, a positioning selection; said positioning selection comprising selection of one of an internal antenna or an external antenna.
 26. The non-transitory machine-readable storage of claim 19, wherein each node antenna arrangement comprises, for each antenna, one or more configuration parameters; said one or more configuration parameters relating to one or more of gain, range, throughput, delay, and error performance.
 27. The non-transitory machine-readable storage of claim 19, wherein said initial antenna setup is configured to optimize performance, based on one or more factors comprising: reducing number of sites for fixed access point (FAP) installation, reducing installation time for each node, increasing overall network coverage, increasing coverage for high traffic areas, and reducing maintenance delays and cost. 